Power control for retransmissions

ABSTRACT

Systems, apparatuses, and methods are described for wireless communications. Wireless communications between a base station and one or more wireless devices are described. A wireless device may use power ramping for transmissions and/or retransmissions. Power ramping may be used during a random access procedure. A wireless device may fail a listen before talk procedure before sending a preamble or a transport block on an unlicensed band. The wireless device may use power ramping to determine a power of transmission of the preamble and/or transport block based on the prior preamble or a transport block transmission. Power ramping may be determined using a power ramping counter value and/or a power ramping step value, which may be shared or associated with the preamble and/or a transport block.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.16/586,515, filed on Sep. 27, 2019, which claims the benefit of U.S.Provisional Application No. 62/737,685, filed on Sep. 27, 2018. Theabove-referenced applications are hereby incorporated by reference intheir entirety.

BACKGROUND

Wireless communications may use radio frequencies within a definedspectrum or bandwidth of frequencies. Some wireless communications mayuse a shared communication medium, such as unlicensed bands shared withother wireless technologies. A wireless device may determine whether acommunication medium is clear, for example, by using a listen beforetalk (LBT) procedure. If the communication medium is busy, the wirelessdevice may not send (e.g., may not transmit) a message and/or may forgoa transmission opportunity. If the communication medium is clear, thewireless device may send (e.g., transmit) a message and/or use thetransmission opportunity.

SUMMARY

The following summary presents a simplified summary of certain features.The summary is not an extensive overview and is not intended to identifykey or critical elements.

Systems, apparatuses, and methods are described for power control ofwireless communications. Wireless communications between a base stationand/or one or more wireless devices are described. Wirelesscommunications may enable multiple opportunities to start and/or restartcommunication between at least two devices, such as a base station and awireless device. A wireless device may use power ramping, such as forretransmissions during a random access (RA) procedure to start and/orrestart communication. A successful transmission of one of a preamble ora transport block (TB) and/or a failure of a transmission the other maycause the wireless device to use power ramping for a retransmission ofthe preamble and/or the TB. A wireless device may fail the transmissionbased on a failure of a first LBT procedure, for example, beforeattempting to send a preamble, and/or a TB, on an unlicensed band. Thewireless device may not send the preamble and/or TB, for example, basedon the failure of the first LBT procedure. The wireless device maycomplete a second LBT procedure, for example, before sending the otherof the preamble, and/or the TB, on the unlicensed band. The wirelessdevice may use power ramping to determine a tpower for transmission ofthe preamble and/or TB, for example, based on a prior transmission of apreamble and/or a TB. Power ramping may be determined (e.g., calculated)using a power value (e.g., a power ramping counter value and/or a powerramping step value). The power value may be shared and/or assocated witha preamble and/or a TB. A wireless device may continue power ramping foreach successful transmission of one of the preamble and/or TB and/orfailure of transmission of another of the one of the preamble and/or TB.A wireless device may use a same power value for power for transmissionsof the preamble and the TB, different power values for the transmissionof the preamble and transmissions of the TB based on different powerramping counter values, and/or different power values for thetransmission of the preamble and transmissions of the TB based on a samepower ramping counter value. Power ramping based on a successfultransmission of one of a preamble or a TB may increase a decodingsuccess rate and/or reduce a number of retransmissions, such that aftera medium becomes available, the transmission may be less likely to failbecause of interference, low power and/or other problems related totransmission power.

These and other features and advantages are described in greater detailbelow.

BRIEF DESCRIPTION OF THE DRAWINGS

Some features are shown by way of example, and not by limitation, in theaccompanying drawings. In the drawings, like numerals reference similarelements.

FIG. 1 shows an example radio access network (RAN) architecture.

FIG. 2A shows an example user plane protocol stack.

FIG. 2B shows an example control plane protocol stack.

FIG. 3 shows an example wireless device and two base stations.

FIG. 4A, FIG. 4B, FIG. 4C, and FIG. 4D show examples of uplink anddownlink signal transmission.

FIG. 5A shows an example uplink channel mapping and example uplinkphysical signals.

FIG. 5B shows an example downlink channel mapping and example downlinkphysical signals.

FIG. 6 shows an example transmission time and/or reception time for acarrier.

FIG. 7A and FIG. 7B show example sets of orthogonal frequency divisionmultiplexing (OFDM) subcarriers.

FIG. 8 shows example OFDM radio resources.

FIG. 9A shows an example channel state information reference signal(CSI-RS) and/or synchronization signal (SS) block transmission in amulti-beam system.

FIG. 9B shows an example downlink beam management procedure.

FIG. 10 shows an example of configured bandwidth parts (BWPs).

FIG. 11A and FIG. 11B show examples of multi connectivity.

FIG. 12 shows an example of a random access procedure.

FIG. 13 shows example medium access control (MAC) entities.

FIG. 14 shows an example RAN architecture.

FIG. 15 shows example radio resource control (RRC) states.

FIG. 16 shows an example of a two-step RA procedure.

FIG. 17A, FIG. 17B, and FIG. 17C show examples of radio resourceallocations of a RA resource and one or more associated radio resources.

FIG. 18 shows an example random access resource configuration.

FIG. 19 shows example field descriptions of a common random accessresource configuration.

FIG. 20 shows an example generic random access resource configuration,and field descriptions.

FIG. 21 shows an example dedicated random access resource configuration.

FIG. 22 shows example field descriptions of a dedicated random accessresource configuration.

FIG. 23 shows example random access occasion mask index values.

FIG. 24 shows an example channel access priority class values.

FIG. 25 shows an example bandwidth part configuration informationelement.

FIG. 26 shows an example serving cell configuration information element.

FIG. 27A, FIG. 27B, and FIG. 27C show examples of RA response (RAR), aMAC subheader with backoff indicator (BI), and a MAC subheader with arandom access preamble identifier (RAPID), respectively.

FIG. 28 shows an example MAC RAR format.

FIG. 29 shows an example RAR format.

FIG. 30A and FIG. 30B show example RAR formats.

FIG. 31 shows an example of a coverage of a cell configured with adownlink and two uplinks.

FIG. 32 shows an example of contention based and contention-free randomaccess (RA) procedures with LBT.

FIG. 33 shows an example of a two-step RA procedure with LBT.

FIG. 34 shows an example of radio resource allocation for a two-step RAprocedure.

FIG. 35 shows an example of one or more LBT procedures for a two-step RAprocedure.

FIG. 36A and FIG. 36B show examples of one or more LBT procedures for atwo-step RA procedure in an unlicensed band.

FIG. 37 shows an example of one or more PRACH occasion configurations.

FIG. 38 shows an example of one or more PRACH occasion configurations.

FIG. 39A and FIG. 39B show examples of start timing of an RAR window.

FIG. 40A, FIG. 40B, and FIG. 40C show examples of start timing of an RARwindow.

FIG. 41 shows an example of a determination of a retransmission.

FIG. 42 shows an example of a retransmission procedure using poweradjustment.

FIG. 43A and FIG. 43B show examples of retransmission procedures usingpower adjustment and listen before talk.

FIG. 44 shows an example of a RA retransmission procedure using poweradjustment.

FIG. 45 shows an example of a RA retransmission procedure using poweradjustment.

FIG. 46 shows example elements of a computing device that may be used toimplement any of the various devices described herein.

DETAILED DESCRIPTION

The accompanying drawings and descriptions provide examples. It is to beunderstood that the examples shown in the drawings and/or described arenon-exclusive and that there are other examples of how features shownand described may be practiced.

Examples are provided for operation of wireless communication systemswhich may be used in the technical field of multicarrier communicationsystems. More particularly, the technology described herein may relateto power control for wireless communications in multicarriercommunication systems.

The following acronyms are used throughout the drawings and/ordescriptions, and are provided below for convenience although otheracronyms may be introduced in the detailed description:

3GPP 3rd Generation Partnership Project

5GC 5G Core Network

ACK Acknowledgement

AMF Access and Mobility Management Function

ARQ Automatic Repeat Request

AS Access Stratum

ASIC Application-Specific Integrated Circuit

BA Bandwidth Adaptation

BCCH Broadcast Control Channel

BCH Broadcast Channel

BFR Beam Failure Recovery

BLER Block Error Rate

BPSK Binary Phase Shift Keying

BSR Buffer Status Report

BWP Bandwidth Part

CA Carrier Aggregation

CC Component Carrier

CCCH Common Control CHannel

CDMA Code Division Multiple Access

CN Core Network

CORESET Control Resource Set

CP Cyclic Prefix

CP-OFDM Cyclic Prefix-Orthogonal Frequency Division Multiplex

C-RNTI Cell-Radio Network Temporary Identifier

CS Configured Scheduling

CSI Channel State Information

CSI-RS Channel State Information-Reference Signal

CQI Channel Quality Indicator

CSS Common Search Space

CU Central Unit

DC Dual Connectivity

DCCH Dedicated Control Channel

DCI Downlink Control Information

DL Downlink

DL-SCH Downlink Shared CHannel

DM-RS DeModulation Reference Signal

DRB Data Radio Bearer

DRX Discontinuous Reception

DTCH Dedicated Traffic Channel

DU Distributed Unit

EPC Evolved Packet Core

E-UTRA Evolved UMTS Terrestrial Radio Access

E-UTRAN Evolved-Universal Terrestrial Radio Access Network

FDD Frequency Division Duplex

FPGA Field Programmable Gate Arrays

F1-C F1-Control plane

F1-U F1-User plane

gNB next generation Node B

HARQ Hybrid Automatic Repeat reQuest

HDL Hardware Description Languages

IE Information Element

IP Internet Protocol

LCH Logical Channel

LCID Logical Channel Identifier

LTE Long Term Evolution

MAC Medium Access Control

MCG Master Cell Group

MCS Modulation and Coding Scheme

MeNB Master evolved Node B

MIB Master Information Block

MME Mobility Management Entity

MN Master Node

NACK Negative Acknowledgement

NAS Non-Access Stratum

NG CP Next Generation Control Plane

NGC Next Generation Core

NG-C NG-Control plane

ng-eNB next generation evolved Node B

NG-U NG-User plane

NR New Radio

NR MAC New Radio MAC

NR PDCP New Radio PDCP

NR PHY New Radio PHYsical

NR RLC New Radio RLC

NR RRC New Radio RRC

NSSAI Network Slice Selection Assistance Information

O&M Operation and Maintenance

OFDM Orthogonal Frequency Division Multiplexing

PBCH Physical Broadcast CHannel

PCC Primary Component Carrier

PCCH Paging Control CHannel

PCell Primary Cell

PCH Paging CHannel

PDCCH Physical Downlink Control CHannel

PDCP Packet Data Convergence Protocol

PDSCH Physical Downlink Shared CHannel

PDU Protocol Data Unit

PHICH Physical HARQ Indicator CHannel

PHY PHYsical

PLMN Public Land Mobile Network

PMI Precoding Matrix Indicator

PRACH Physical Random Access CHannel

PRB Physical Resource Block

PSCell Primary Secondary Cell

PSS Primary Synchronization Signal

pTAG primary Timing Advance Group

PT-RS Phase Tracking Reference Signal

PUCCH Physical Uplink Control CHannel

PUSCH Physical Uplink Shared CHannel

QAM Quadrature Amplitude Modulation

QCLed Quasi-Co-Located

QCL Quasi-Co-Location

QFI Quality of Service Indicator

QoS Quality of Service

QPSK Quadrature Phase Shift Keying

RA Random Access

RACH Random Access CHannel

RAN Radio Access Network

RAT Radio Access Technology

RA-RNTI Random Access-Radio Network Temporary Identifier

RB Resource Blocks

RBG Resource Block Groups

RI Rank indicator

RLC Radio Link Control

RLM Radio Link Monitoring

RRC Radio Resource Control

RS Reference Signal

RSRP Reference Signal Received Power

SCC Secondary Component Carrier

SCell Secondary Cell

SCG Secondary Cell Group

SC-FDMA Single Carrier-Frequency Division Multiple Access

SDAP Service Data Adaptation Protocol

SDU Service Data Unit

SeNB Secondary evolved Node B

SFN System Frame Number

S-GW Serving GateWay

SI System Information

SIB System Information Block

SINR Signal-to-Interference-plus-Noise Ratio

SMF Session Management Function

SN Secondary Node

SpCell Special Cell

SR Scheduling Request

SRB Signaling Radio Bearer

SRS Sounding Reference Signal

SS Synchronization Signal

SSB Synchronization Signal Block

SSS Secondary Synchronization Signal

sTAG secondary Timing Advance Group

TA Timing Advance

TAG Timing Advance Group

TAI Tracking Area Identifier

TAT Time Alignment Timer

TB Transport Block

TC-RNTI Temporary Cell-Radio Network Temporary Identifier

TCI Transmission Configuration Indication

TDD Time Division Duplex

TDMA Time Division Multiple Access

TRP Transmission and Receiving Point

TTI Transmission Time Interval

UCI Uplink Control Information

UE User Equipment

UL Uplink

UL-SCH Uplink Shared CHannel

UPF User Plane Function

UPGW User Plane Gateway

VHDL VHSIC Hardware Description Language

Xn-C Xn-Control plane

Xn-U Xn-User plane

Examples described herein may be implemented using various physicallayer modulation and transmission mechanisms. Example transmissionmechanisms may include, but are not limited to: Code Division MultipleAccess (CDMA), Orthogonal Frequency Division Multiple Access (OFDMA),Time Division Multiple Access (TDMA), Wavelet technologies, and/or thelike. Hybrid transmission mechanisms such as TDMA/CDMA, and/or OFDM/CDMAmay be used. Various modulation schemes may be used for signaltransmission in the physical layer. Examples of modulation schemesinclude, but are not limited to: phase, amplitude, code, a combinationof these, and/or the like. An example radio transmission method mayimplement Quadrature Amplitude Modulation (QAM) using Binary Phase ShiftKeying (BPSK), Quadrature Phase Shift Keying (QPSK), 16-QAM, 64-QAM,256-QAM, and/or the like. Physical radio transmission may be enhanced bydynamically or semi-dynamically changing the modulation and codingscheme, for example, depending on transmission requirements and/or radioconditions.

FIG. 1 shows an example Radio Access Network (RAN) architecture. A RANnode may comprise a next generation Node B (gNB) (e.g., 120A, 120B)providing New Radio (NR) user plane and control plane protocolterminations towards a first wireless device (e.g., 110A). A RAN nodemay comprise a base station such as a next generation evolved Node B(ng-eNB) (e.g., 120C, 120D), providing Evolved UMTS Terrestrial RadioAccess (E-UTRA) user plane and control plane protocol terminationstowards a second wireless device (e.g., 110B). A first wireless device110A may communicate with a base station, such as a gNB 120A, over a Uuinterface. A second wireless device 110B may communicate with a basestation, such as an ng-eNB 120D, over a Uu interface. The wirelessdevices 110A and/or 110B may be structurally similar to wireless devicesshown in and/or described in connection with other drawing figures. TheNode B 120A, the Node B 120B, the Node B 120C, and/or the Node B 120Dmay be structurally similar to Nodes B and/or base stations shown inand/or described in connection with other drawing figures.

A base station, such as a gNB (e.g., 120A, 120B, etc.) and/or an ng-eNB(e.g., 120C, 120D, etc.) may host functions such as radio resourcemanagement and scheduling, IP header compression, encryption andintegrity protection of data, selection of Access and MobilityManagement Function (AMF) at wireless device (e.g., User Equipment (UE))attachment, routing of user plane and control plane data, connectionsetup and release, scheduling and transmission of paging messages (e.g.,originated from the AMF), scheduling and transmission of systembroadcast information (e.g., originated from the AMF or Operation andMaintenance (O&M)), measurement and measurement reporting configuration,transport level packet marking in the uplink, session management,support of network slicing, Quality of Service (QoS) flow management andmapping to data radio bearers, support of wireless devices in aninactive state (e.g., RRC_INACTIVE state), distribution function forNon-Access Stratum (NAS) messages, RAN sharing, dual connectivity,and/or tight interworking between NR and E-UTRA.

One or more first base stations (e.g., gNBs 120A and 120B) and/or one ormore second base stations (e.g., ng-eNBs 120C and 120D) may beinterconnected with each other via Xn interface. A first base station(e.g., gNB 120A, 120B, etc.) or a second base station (e.g., ng-eNB120C, 120D, etc.) may be connected via NG interfaces to a network, suchas a 5G Core Network (5GC). A 5GC may comprise one or more AMF/User PlanFunction (UPF) functions (e.g., 130A and/or 130B). A base station (e.g.,a gNB and/or an ng-eNB) may be connected to a UPF via an NG-User plane(NG-U) interface. The NG-U interface may provide delivery (e.g.,non-guaranteed delivery) of user plane Protocol Data Units (PDUs)between a RAN node and the UPF. A base station (e.g., a gNB and/or anng-eNB) may be connected to an AMF via an NG-Control plane (NG-C)interface. The NG-C interface may provide, for example, NG interfacemanagement, wireless device (e.g., UE) context management, wirelessdevice (e.g., UE) mobility management, transport of NAS messages,paging, PDU session management, configuration transfer, and/or warningmessage transmission, combinations thereof, and/or the like.

A UPF may host functions such as anchor point for intra-/inter-RadioAccess Technology (RAT) mobility (e.g., if applicable), external PDUsession point of interconnect to data network, packet routing andforwarding, packet inspection and user plane part of policy ruleenforcement, traffic usage reporting, uplink classifier to supportrouting traffic flows to a data network, branching point to supportmulti-homed PDU session, quality of service (QoS) handling for userplane, packet filtering, gating, Uplink (UL)/Downlink (DL) rateenforcement, uplink traffic verification (e.g., Service Data Flow (SDF)to QoS flow mapping), downlink packet buffering, and/or downlink datanotification triggering.

An AMF may host functions such as NAS signaling termination, NASsignaling security, Access Stratum (AS) security control, inter CoreNetwork (CN) node signaling (e.g., for mobility between 3rd GenerationPartnership Project (3GPP) access networks), idle mode wireless devicereachability (e.g., control and execution of paging retransmission),registration area management, support of intra-system and inter-systemmobility, access authentication, access authorization including check ofroaming rights, mobility management control (e.g., subscription and/orpolicies), support of network slicing, and/or Session ManagementFunction (SMF) selection.

FIG. 2A shows an example user plane protocol stack. A Service DataAdaptation Protocol (SDAP) (e.g., 211 and 221), Packet Data ConvergenceProtocol (PDCP) (e.g., 212 and 222), Radio Link Control (RLC) (e.g., 213and 223), and Medium Access Control (MAC) (e.g., 214 and 224) sublayers,and a Physical (PHY) (e.g., 215 and 225) layer, may be terminated in awireless device (e.g., 110) and in a base station (e.g., 120) on anetwork side. A PHY layer may provide transport services to higherlayers (e.g., MAC, RRC, etc.). Services and/or functions of a MACsublayer may comprise mapping between logical channels and transportchannels, multiplexing and/or demultiplexing of MAC Service Data Units(SDUs) belonging to the same or different logical channels into and/orfrom Transport Blocks (TBs) delivered to and/or from the PHY layer,scheduling information reporting, error correction through HybridAutomatic Repeat request (HARQ) (e.g., one HARQ entity per carrier forCarrier Aggregation (CA)), priority handling between wireless devicessuch as by using dynamic scheduling, priority handling between logicalchannels of a wireless device such as by using logical channelprioritization, and/or padding. A MAC entity may support one or multiplenumerologies and/or transmission timings. Mapping restrictions in alogical channel prioritization may control which numerology and/ortransmission timing a logical channel may use. An RLC sublayer maysupport transparent mode (TM), unacknowledged mode (UM), and/oracknowledged mode (AM) transmission modes. The RLC configuration may beper logical channel with no dependency on numerologies and/orTransmission Time Interval (TTI) durations. Automatic Repeat Request(ARQ) may operate on any of the numerologies and/or TTI durations withwhich the logical channel is configured. Services and functions of thePDCP layer for the user plane may comprise, for example, sequencenumbering, header compression and decompression, transfer of user data,reordering and duplicate detection, PDCP PDU routing (e.g., such as forsplit bearers), retransmission of PDCP SDUs, ciphering, deciphering andintegrity protection, PDCP SDU discard, PDCP re-establishment and datarecovery for RLC AM, and/or duplication of PDCP PDUs. Services and/orfunctions of SDAP may comprise, for example, mapping between a QoS flowand a data radio bearer. Services and/or functions of SDAP may comprisemapping a Quality of Service Indicator (QFI) in DL and UL packets. Aprotocol entity of SDAP may be configured for an individual PDU session.

FIG. 2B shows an example control plane protocol stack. A PDCP (e.g., 233and 242), RLC (e.g., 234 and 243), and MAC (e.g., 235 and 244)sublayers, and a PHY (e.g., 236 and 245) layer, may be terminated in awireless device (e.g., 110), and in a base station (e.g., 120) on anetwork side, and perform service and/or functions described above. RRC(e.g., 232 and 241) may be terminated in a wireless device and a basestation on a network side. Services and/or functions of RRC may comprisebroadcast of system information related to AS and/or NAS; paging (e.g.,initiated by a 5GC or a RAN); establishment, maintenance, and/or releaseof an RRC connection between the wireless device and RAN; securityfunctions such as key management, establishment, configuration,maintenance, and/or release of Signaling Radio Bearers (SRBs) and DataRadio Bearers (DRBs); mobility functions; QoS management functions;wireless device measurement reporting and control of the reporting;detection of and recovery from radio link failure; and/or NAS messagetransfer to/from NAS from/to a wireless device. NAS control protocol(e.g., 231 and 251) may be terminated in the wireless device and AMF(e.g., 130) on a network side. NAS control protocol may performfunctions such as authentication, mobility management between a wirelessdevice and an AMF (e.g., for 3GPP access and non-3GPP access), and/orsession management between a wireless device and an SMF (e.g., for 3GPPaccess and non-3GPP access).

A base station may configure a plurality of logical channels for awireless device. A logical channel of the plurality of logical channelsmay correspond to a radio bearer. The radio bearer may be associatedwith a QoS requirement. A base station may configure a logical channelto be mapped to one or more TTIs and/or numerologies in a plurality ofTTIs and/or numerologies. The wireless device may receive DownlinkControl Information (DCI) via a Physical Downlink Control CHannel(PDCCH) indicating an uplink grant. The uplink grant may be for a firstTTI and/or a first numerology and may indicate uplink resources fortransmission of a TB. The base station may configure each logicalchannel in the plurality of logical channels with one or more parametersto be used by a logical channel prioritization procedure at the MAClayer of the wireless device. The one or more parameters may comprise,for example, priority, prioritized bit rate, etc. A logical channel inthe plurality of logical channels may correspond to one or more bufferscomprising data associated with the logical channel. The logical channelprioritization procedure may allocate the uplink resources to one ormore first logical channels in the plurality of logical channels and/orto one or more MAC Control Elements (CEs). The one or more first logicalchannels may be mapped to the first TTI and/or the first numerology. TheMAC layer at the wireless device may multiplex one or more MAC CEsand/or one or more MAC SDUs (e.g., logical channel) in a MAC PDU (e.g.,TB). The MAC PDU may comprise a MAC header comprising a plurality of MACsub-headers. A MAC sub-header in the plurality of MAC sub-headers maycorrespond to a MAC CE or a MAC SUD (e.g., logical channel) in the oneor more MAC CEs and/or in the one or more MAC SDUs. A MAC CE and/or alogical channel may be configured with a Logical Channel IDentifier(LCID). An LCID for a logical channel and/or a MAC CE may be fixedand/or pre-configured. An LCID for a logical channel and/or MAC CE maybe configured for the wireless device by the base station. The MACsub-header corresponding to a MAC CE and/or a MAC SDU may comprise anLCID associated with the MAC CE and/or the MAC SDU.

A base station may activate, deactivate, and/or impact one or moreprocesses (e.g., set values of one or more parameters of the one or moreprocesses or start and/or stop one or more timers of the one or moreprocesses) at the wireless device, for example, by using one or more MACcommands The one or more MAC commands may comprise one or more MACcontrol elements. The one or more processes may comprise activationand/or deactivation of PDCP packet duplication for one or more radiobearers. The base station may send (e.g., transmit) a MAC CE comprisingone or more fields. The values of the fields may indicate activationand/or deactivation of PDCP duplication for the one or more radiobearers. The one or more processes may comprise Channel StateInformation (CSI) transmission of on one or more cells. The base stationmay send (e.g., transmit) one or more MAC CEs indicating activationand/or deactivation of the CSI transmission on the one or more cells.The one or more processes may comprise activation and/or deactivation ofone or more secondary cells. The base station may send (e.g., transmit)a MAC CE indicating activation and/or deactivation of one or moresecondary cells. The base station may send (e.g., transmit) one or moreMAC CEs indicating starting and/or stopping of one or more DiscontinuousReception (DRX) timers at the wireless device. The base station may send(e.g., transmit) one or more MAC CEs that indicate one or more timingadvance values for one or more Timing Advance Groups (TAGs).

FIG. 3 shows an example of base stations (base station 1, 120A, and basestation 2, 120B) and a wireless device 110. The wireless device 110 maycomprise a UE or any other wireless device. The base station (e.g.,120A, 120B) may comprise a Node B, eNB, gNB, ng-eNB, or any other basestation. A wireless device and/or a base station may perform one or morefunctions of a relay node. The base station 1, 120A, may comprise atleast one communication interface 320A (e.g., a wireless modem, anantenna, a wired modem, and/or the like), at least one processor 321A,and at least one set of program code instructions 323A that may bestored in non-transitory memory 322A and executable by the at least oneprocessor 321A. The base station 2, 120B, may comprise at least onecommunication interface 320B, at least one processor 321B, and at leastone set of program code instructions 323B that may be stored innon-transitory memory 322B and executable by the at least one processor321B.

A base station may comprise any number of sectors, for example: 1, 2, 3,4, or 6 sectors. A base station may comprise any number of cells, forexample, ranging from 1 to 50 cells or more. A cell may be categorized,for example, as a primary cell or secondary cell. At Radio ResourceControl (RRC) connection establishment, re-establishment, handover,etc., a serving cell may provide NAS (non-access stratum) mobilityinformation (e.g., Tracking Area Identifier (TAI)). At RRC connectionre-establishment and/or handover, a serving cell may provide securityinput. This serving cell may be referred to as the Primary Cell (PCell).In the downlink, a carrier corresponding to the PCell may be a DLPrimary Component Carrier (PCC). In the uplink, a carrier may be an ULPCC. Secondary Cells (SCells) may be configured to form together with aPCell a set of serving cells, for example, depending on wireless devicecapabilities. In a downlink, a carrier corresponding to an SCell may bea downlink secondary component carrier (DL SCC). In an uplink, a carriermay be an uplink secondary component carrier (UL SCC). An SCell may ormay not have an uplink carrier.

A cell, comprising a downlink carrier and optionally an uplink carrier,may be assigned a physical cell ID and/or a cell index. A carrier(downlink and/or uplink) may belong to one cell. The cell ID and/or cellindex may identify the downlink carrier and/or uplink carrier of thecell (e.g., depending on the context it is used). A cell ID may beequally referred to as a carrier ID, and a cell index may be referred toas a carrier index. A physical cell ID and/or a cell index may beassigned to a cell. A cell ID may be determined using a synchronizationsignal transmitted via a downlink carrier. A cell index may bedetermined using RRC messages. A first physical cell ID for a firstdownlink carrier may indicate that the first physical cell ID is for acell comprising the first downlink carrier. The same concept may beused, for example, with carrier activation and/or deactivation (e.g.,secondary cell activation and/or deactivation). A first carrier that isactivated may indicate that a cell comprising the first carrier isactivated.

A base station may send (e.g., transmit) to a wireless device one ormore messages (e.g., RRC messages) comprising a plurality ofconfiguration parameters for one or more cells. One or more cells maycomprise at least one primary cell and at least one secondary cell. AnRRC message may be broadcasted and/or unicasted to the wireless device.Configuration parameters may comprise common parameters and dedicatedparameters.

Services and/or functions of an RRC sublayer may comprise at least oneof: broadcast of system information related to AS and/or NAS; paginginitiated by a 5GC and/or an NG-RAN; establishment, maintenance, and/orrelease of an RRC connection between a wireless device and an NG-RAN,which may comprise at least one of addition, modification, and/orrelease of carrier aggregation; and/or addition, modification, and/orrelease of dual connectivity in NR or between E-UTRA and NR. Servicesand/or functions of an RRC sublayer may comprise at least one ofsecurity functions comprising key management; establishment,configuration, maintenance, and/or release of Signaling Radio Bearers(SRBs) and/or Data Radio Bearers (DRBs); mobility functions which maycomprise at least one of a handover (e.g., intra NR mobility orinter-RAT mobility) and/or a context transfer; and/or a wireless devicecell selection and/or reselection and/or control of cell selection andreselection. Services and/or functions of an RRC sublayer may compriseat least one of QoS management functions; a wireless device measurementconfiguration/reporting; detection of and/or recovery from radio linkfailure; and/or NAS message transfer to and/or from a core networkentity (e.g., AMF, Mobility Management Entity (MME)) from and/or to thewireless device.

An RRC sublayer may support an RRC_Idle state, an RRC_Inactive state,and/or an RRC_Connected state for a wireless device. In an RRC_Idlestate, a wireless device may perform at least one of: Public Land MobileNetwork (PLMN) selection; receiving broadcasted system information; cellselection and/or re-selection; monitoring and/or receiving a paging formobile terminated data initiated by SGC; paging for mobile terminateddata area managed by SGC; and/or DRX for CN paging configured via NAS.In an RRC_Inactive state, a wireless device may perform at least one of:receiving broadcasted system information; cell selection and/orre-selection; monitoring and/or receiving a RAN and/or CN paginginitiated by an NG-RAN and/or a SGC; RAN-based notification area (RNA)managed by an NG-RAN; and/or DRX for a RAN and/or CN paging configuredby NG-RAN/NAS. In an RRC_Idle state of a wireless device, a base station(e.g., NG-RAN) may keep a 5GC-NG-RAN connection (e.g., both C/U-planes)for the wireless device; and/or store a wireless device AS context forthe wireless device. In an RRC_Connected state of a wireless device, abase station (e.g., NG-RAN) may perform at least one of: establishmentof 5GC-NG-RAN connection (both C/U-planes) for the wireless device;storing a UE AS context for the wireless device; send (e.g., transmit)and/or receive of unicast data to and/or from the wireless device;and/or network-controlled mobility based on measurement results receivedfrom the wireless device. In an RRC_Connected state of a wirelessdevice, an NG-RAN may know a cell to which the wireless device belongs.

System information (SI) may be divided into minimum SI and other SI. Theminimum SI may be periodically broadcast. The minimum SI may comprisebasic information required for initial access and/or information foracquiring any other SI broadcast periodically and/or provisionedon-demand (e.g., scheduling information). The other SI may either bebroadcast, and/or be provisioned in a dedicated manner, such as eithertriggered by a network and/or upon request from a wireless device. Aminimum SI may be transmitted via two different downlink channels usingdifferent messages (e.g., MasterinformationBlock andSystemInformationBlockTyp1). Another SI may be transmitted viaSystemInformationBlockType2. For a wireless device in an RRC_Connectedstate, dedicated RRC signaling may be used for the request and deliveryof the other SI. For the wireless device in the RRC_Idle state and/or inthe RRC_Inactive state, the request may trigger a RA procedure.

A wireless device may report its radio access capability information,which may be static. A base station may request one or more indicationsof capabilities for a wireless device to report based on bandinformation. A temporary capability restriction request may be sent bythe wireless device (e.g., if allowed by a network) to signal thelimited availability of some capabilities (e.g., due to hardwaresharing, interference, and/or overheating) to the base station. The basestation may confirm or reject the request. The temporary capabilityrestriction may be transparent to 5GC (e.g., static capabilities may bestored in 5GC).

A wireless device may have an RRC connection with a network, forexample, if CA is configured. At RRC connection establishment,re-establishment, and/or handover procedures, a serving cell may provideNAS mobility information. At RRC connection re-establishment and/orhandover, a serving cell may provide a security input. This serving cellmay be referred to as the PCell. SCells may be configured to formtogether with the PCell a set of serving cells, for example, dependingon the capabilities of the wireless device. The configured set ofserving cells for the wireless device may comprise a PCell and one ormore SCells.

The reconfiguration, addition, and/or removal of SCells may be performedby RRC messaging. At intra-NR handover, RRC may add, remove, and/orreconfigure SCells for usage with the target PCell. Dedicated RRCsignaling may be used (e.g., if adding a new SCell) to send all requiredsystem information of the SCell (e.g., if in connected mode, wirelessdevices may not acquire broadcasted system information directly from theSCells).

The purpose of an RRC connection reconfiguration procedure may be tomodify an RRC connection, (e.g., to establish, modify, and/or releaseRBs; to perform handover; to setup, modify, and/or release measurements,for example, to add, modify, and/or release SCells and cell groups). NASdedicated information may be transferred from the network to thewireless device, for example, as part of the RRC connectionreconfiguration procedure. The RRCConnectionReconfiguration message maybe a command to modify an RRC connection. One or more RRC messages mayconvey information for measurement configuration, mobility control,and/or radio resource configuration (e.g., RBs, MAC main configuration,and/or physical channel configuration), which may comprise anyassociated dedicated NAS information and/or security configuration. Thewireless device may perform an SCell release, for example, if thereceived RRC Connection Reconfiguration message includes thesCellToReleaseList. The wireless device may perform SCell additions ormodification, for example, if the received RRC ConnectionReconfiguration message includes the sCellToAddModList.

An RRC connection establishment, reestablishment, and/or resumeprocedure may be to establish, reestablish, and/or resume an RRCconnection, respectively. An RRC connection establishment procedure maycomprise SRB1 establishment. The RRC connection establishment proceduremay be used to transfer the initial NAS dedicated information and/ormessage from a wireless device to an E-UTRAN. TheRRCConnectionReestablishment message may be used to re-establish SRB1.

A measurement report procedure may be used to transfer measurementresults from a wireless device to an NG-RAN. The wireless device mayinitiate a measurement report procedure, for example, after successfulsecurity activation. A measurement report message may be used to send(e.g., transmit) measurement results.

The wireless device 110 may comprise at least one communicationinterface 310 (e.g., a wireless modem, an antenna, and/or the like), atleast one processor 314, and at least one set of program codeinstructions 316 that may be stored in non-transitory memory 315 andexecutable by the at least one processor 314. The wireless device 110may further comprise at least one of at least one speaker and/ormicrophone 311, at least one keypad 312, at least one display and/ortouchpad 313, at least one power source 317, at least one globalpositioning system (GPS) chipset 318, and/or other peripherals 319.

The processor 314 of the wireless device 110, the processor 321A of thebase station 1 120A, and/or the processor 321B of the base station 2120B may comprise at least one of a general-purpose processor, a digitalsignal processor (DSP), a controller, a microcontroller, an applicationspecific integrated circuit (ASIC), a field programmable gate array(FPGA) and/or other programmable logic device, discrete gate and/ortransistor logic, discrete hardware components, and/or the like. Theprocessor 314 of the wireless device 110, the processor 321A in basestation 1 120A, and/or the processor 321B in base station 2 120B mayperform at least one of signal coding and/or processing, dataprocessing, power control, input/output processing, and/or any otherfunctionality that may enable the wireless device 110, the base station1 120A and/or the base station 2 120B to operate in a wirelessenvironment.

The processor 314 of the wireless device 110 may be connected to and/orin communication with the speaker and/or microphone 311, the keypad 312,and/or the display and/or touchpad 313. The processor 314 may receiveuser input data from and/or provide user output data to the speakerand/or microphone 311, the keypad 312, and/or the display and/ortouchpad 313. The processor 314 in the wireless device 110 may receivepower from the power source 317 and/or may be configured to distributethe power to the other components in the wireless device 110. The powersource 317 may comprise at least one of one or more dry cell batteries,solar cells, fuel cells, and/or the like. The processor 314 may beconnected to the GPS chipset 318. The GPS chipset 318 may be configuredto provide geographic location information of the wireless device 110.

The processor 314 of the wireless device 110 may further be connected toand/or in communication with other peripherals 319, which may compriseone or more software and/or hardware modules that may provide additionalfeatures and/or functionalities. For example, the peripherals 319 maycomprise at least one of an accelerometer, a satellite transceiver, adigital camera, a universal serial bus (USB) port, a hands-free headset,a frequency modulated (FM) radio unit, a media player, an Internetbrowser, and/or the like.

The communication interface 320A of the base station 1, 120A, and/or thecommunication interface 320B of the base station 2, 120B, may beconfigured to communicate with the communication interface 310 of thewireless device 110, for example, via a wireless link 330A and/or via awireless link 330B, respectively. The communication interface 320A ofthe base station 1, 120A, may communicate with the communicationinterface 320B of the base station 2 and/or other RAN and/or corenetwork nodes.

The wireless link 330A and/or the wireless link 330B may comprise atleast one of a bi-directional link and/or a directional link. Thecommunication interface 310 of the wireless device 110 may be configuredto communicate with the communication interface 320A of the base station1 120A and/or with the communication interface 320B of the base station2 120B. The base station 1 120A and the wireless device 110, and/or thebase station 2 120B and the wireless device 110, may be configured tosend and receive TBs, for example, via the wireless link 330A and/or viathe wireless link 330B, respectively. The wireless link 330A and/or thewireless link 330B may use at least one frequency carrier.Transceiver(s) may be used. A transceiver may be a device that comprisesboth a transmitter and a receiver. Transceivers may be used in devicessuch as wireless devices, base stations, relay nodes, computing devices,and/or the like. Radio technology may be implemented in thecommunication interface 310, 320A, and/or 320B, and the wireless link330A and/or 330B. The radio technology may comprise one or more elementsshown in FIG. 4A, FIG. 4B, FIG. 4C, FIG. 4D, FIG. 6, FIG. 7A, FIG. 7B,FIG. 8, and associated text, described below.

Other nodes in a wireless network (e.g., AMF, UPF, SMF, etc.) maycomprise one or more communication interfaces, one or more processors,and memory storing instructions. A node (e.g., wireless device, basestation, AMF, SMF, UPF, servers, switches, antennas, and/or the like)may comprise one or more processors, and memory storing instructionsthat when executed by the one or more processors causes the node toperform certain processes and/or functions. Single-carrier and/ormulti-carrier communication operation may be performed. A non-transitorytangible computer readable media may comprise instructions executable byone or more processors to cause operation of single-carrier and/ormulti-carrier communications. An article of manufacture may comprise anon-transitory tangible computer readable machine-accessible mediumhaving instructions encoded thereon for enabling programmable hardwareto cause a node to enable operation of single-carrier and/ormulti-carrier communications. The node may include processors, memory,interfaces, and/or the like.

An interface may comprise at least one of a hardware interface, afirmware interface, a software interface, and/or a combination thereof.The hardware interface may comprise connectors, wires, and/or electronicdevices such as drivers, amplifiers, and/or the like. The softwareinterface may comprise code stored in a memory device to implementprotocol(s), protocol layers, communication drivers, device drivers,combinations thereof, and/or the like. The firmware interface maycomprise a combination of embedded hardware and/or code stored in(and/or in communication with) a memory device to implement connections,electronic device operations, protocol(s), protocol layers,communication drivers, device drivers, hardware operations, combinationsthereof, and/or the like.

A communication network may comprise the wireless device 110, the basestation 1, 120A, the base station 2, 120B, and/or any other device. Thecommunication network may comprise any number and/or type of devices,such as, for example, computing devices, wireless devices, mobiledevices, handsets, tablets, laptops, internet of things (IoT) devices,hotspots, cellular repeaters, computing devices, and/or, more generally,user equipment (e.g., UE). Although one or more of the above types ofdevices may be referenced herein (e.g., UE, wireless device, computingdevice, etc.), it should be understood that any device herein maycomprise any one or more of the above types of devices or similardevices. The communication network, and any other network referencedherein, may comprise an LTE network, a 5G network, or any other networkfor wireless communications. Apparatuses, systems, and/or methodsdescribed herein may generally be described as implemented on one ormore devices (e.g., wireless device, base station, eNB, gNB, computingdevice, etc.), in one or more networks, but it will be understood thatone or more features and steps may be implemented on any device and/orin any network. As used throughout, the term “base station” may compriseone or more of: a base station, a node, a Node B, a gNB, an eNB, anng-eNB, a relay node (e.g., an integrated access and backhaul (IAB)node), a donor node (e.g., a donor eNB, a donor gNB, etc.), an accesspoint (e.g., a WiFi access point), a computing device, a device capableof wirelessly communicating, or any other device capable of sendingand/or receiving signals. As used throughout, the term “wireless device”may comprise one or more of: a UE, a handset, a mobile device, acomputing device, a node, a device capable of wirelessly communicating,or any other device capable of sending and/or receiving signals. Anyreference to one or more of these terms/devices also considers use ofany other term/device mentioned above.

FIG. 4A, FIG. 4B, FIG. 4C and FIG. 4D show examples of uplink anddownlink signal transmission. FIG. 4A shows an example uplinktransmitter for at least one physical channel A baseband signalrepresenting a physical uplink shared channel may perform one or morefunctions. The one or more functions may comprise at least one of:scrambling (e.g., by Scrambling); modulation of scrambled bits togenerate complex-valued symbols (e.g., by a Modulation mapper); mappingof the complex-valued modulation symbols onto one or severaltransmission layers (e.g., by a Layer mapper); transform precoding togenerate complex-valued symbols (e.g., by a Transform precoder);precoding of the complex-valued symbols (e.g., by a Precoder); mappingof precoded complex-valued symbols to resource elements (e.g., by aResource element mapper); generation of complex-valued time-domainSingle Carrier-Frequency Division Multiple Access (SC-FDMA) or CP-OFDMsignal for an antenna port (e.g., by a signal gen.); and/or the like. ASC-FDMA signal for uplink transmission may be generated, for example, iftransform precoding is enabled. A CP-OFDM signal for uplink transmissionmay be generated by FIG. 4A, for example, if transform precoding is notenabled. These functions are shown as examples and other mechanisms maybe implemented.

FIG. 4B shows an example of modulation and up-conversion to the carrierfrequency of a complex-valued SC-FDMA or CP-OFDM baseband signal for anantenna port and/or for the complex-valued Physical Random AccessCHannel (PRACH) baseband signal. Filtering may be performed prior totransmission.

FIG. 4C shows an example of downlink transmissions. The baseband signalrepresenting a downlink physical channel may perform one or morefunctions. The one or more functions may comprise: scrambling of codedbits in a codeword to be transmitted on a physical channel (e.g., byScrambling); modulation of scrambled bits to generate complex-valuedmodulation symbols (e.g., by a Modulation mapper); mapping of thecomplex-valued modulation symbols onto one or several transmissionlayers (e.g., by a Layer mapper); precoding of the complex-valuedmodulation symbols on a layer for transmission on the antenna ports(e.g., by Precoding); mapping of complex-valued modulation symbols foran antenna port to resource elements (e.g., by a Resource elementmapper); generation of complex-valued time-domain OFDM signal for anantenna port (e.g., by an OFDM signal gen.); and/or the like. Thesefunctions are shown as examples and other mechanisms may be implemented.

A base station may send (e.g., transmit) a first symbol and a secondsymbol on an antenna port, to a wireless device. The wireless device mayinfer the channel (e.g., fading gain, multipath delay, etc.) forconveying the second symbol on the antenna port, from the channel forconveying the first symbol on the antenna port. A first antenna port anda second antenna port may be quasi co-located, for example, if one ormore large-scale properties of the channel over which a first symbol onthe first antenna port is conveyed may be inferred from the channel overwhich a second symbol on a second antenna port is conveyed. The one ormore large-scale properties may comprise at least one of: delay spread;Doppler spread; Doppler shift; average gain; average delay; and/orspatial receiving (Rx) parameters.

FIG. 4D shows an example modulation and up-conversion to the carrierfrequency of the complex-valued OFDM baseband signal for an antennaport. Filtering may be performed prior to transmission.

FIG. 5A shows example uplink channel mapping and example uplink physicalsignals. A physical layer may provide one or more information transferservices to a MAC and/or one or more higher layers. The physical layermay provide the one or more information transfer services to the MAC viaone or more transport channels. An information transfer service mayindicate how and/or with what characteristics data is transferred overthe radio interface.

Uplink transport channels may comprise an Uplink-Shared CHannel (UL-SCH)501 and/or a Random Access CHannel (RACH) 502. A wireless device maysend (e.g., transmit) one or more uplink DM-RSs 506 to a base stationfor channel estimation, for example, for coherent demodulation of one ormore uplink physical channels (e.g., PUSCH 503 and/or PUCCH 504). Thewireless device may send (e.g., transmit) to a base station at least oneuplink DM-RS 506 with PUSCH 503 and/or PUCCH 504, wherein the at leastone uplink DM-RS 506 may be spanning a same frequency range as acorresponding physical channel. The base station may configure thewireless device with one or more uplink DM-RS configurations. At leastone DM-RS configuration may support a front-loaded DM-RS pattern. Afront-loaded DM-RS may be mapped over one or more OFDM symbols (e.g., 1or 2 adjacent OFDM symbols). One or more additional uplink DM-RS may beconfigured to send (e.g., transmit) at one or more symbols of a PUSCHand/or PUCCH. The base station may semi-statically configure thewireless device with a maximum number of front-loaded DM-RS symbols forPUSCH and/or PUCCH. The wireless device may schedule a single-symbolDM-RS and/or double symbol DM-RS based on a maximum number offront-loaded DM-RS symbols, wherein the base station may configure thewireless device with one or more additional uplink DM-RS for PUSCHand/or PUCCH. A new radio network may support, for example, at least forCP-OFDM, a common DM-RS structure for DL and UL, wherein a DM-RSlocation, DM-RS pattern, and/or scrambling sequence may be same ordifferent.

Whether or not an uplink PT-RS 507 is present may depend on an RRCconfiguration. A presence of the uplink PT-RS may be wirelessdevice-specifically configured. A presence and/or a pattern of theuplink PT-RS 507 in a scheduled resource may be wirelessdevice-specifically configured by a combination of RRC signaling and/orassociation with one or more parameters used for other purposes (e.g.,Modulation and Coding Scheme (MCS)) which may be indicated by DCI. Ifconfigured, a dynamic presence of uplink PT-RS 507 may be associatedwith one or more DCI parameters comprising at least a MCS. A radionetwork may support a plurality of uplink PT-RS densities defined intime/frequency domain. If present, a frequency domain density may beassociated with at least one configuration of a scheduled bandwidth. Awireless device may assume a same precoding for a DMRS port and a PT-RSport. A number of PT-RS ports may be less than a number of DM-RS portsin a scheduled resource. The uplink PT-RS 507 may be confined in thescheduled time/frequency duration for a wireless device.

A wireless device may send (e.g., transmit) an SRS 508 to a base stationfor channel state estimation, for example, to support uplink channeldependent scheduling and/or link adaptation. The SRS 508 sent (e.g.,transmitted) by the wireless device may allow for the base station toestimate an uplink channel state at one or more different frequencies. Abase station scheduler may use an uplink channel state to assign one ormore resource blocks of a certain quality (e.g., above a qualitythreshold) for an uplink PUSCH transmission from the wireless device.The base station may semi-statically configure the wireless device withone or more SRS resource sets. For an SRS resource set, the base stationmay configure the wireless device with one or more SRS resources. An SRSresource set applicability may be configured by a higher layer (e.g.,RRC) parameter. An SRS resource in each of one or more SRS resource setsmay be sent (e.g., transmitted) at a time instant, for example, if ahigher layer parameter indicates beam management. The wireless devicemay send (e.g., transmit) one or more SRS resources in different SRSresource sets simultaneously. A new radio network may support aperiodic,periodic, and/or semi-persistent SRS transmissions. The wireless devicemay send (e.g., transmit) SRS resources, for example, based on one ormore trigger types. The one or more trigger types may comprise higherlayer signaling (e.g., RRC) and/or one or more DCI formats (e.g., atleast one DCI format may be used for a wireless device to select atleast one of one or more configured SRS resource sets). An SRS triggertype 0 may refer to an SRS triggered based on a higher layer signaling.An SRS trigger type 1 may refer to an SRS triggered based on one or moreDCI formats. The wireless device may be configured to send (e.g.,transmit) the SRS 508 after a transmission of PUSCH 503 andcorresponding uplink DM-RS 506, for example, if PUSCH 503 and the SRS508 are transmitted in a same slot.

A base station may semi-statically configure a wireless device with oneor more SRS configuration parameters indicating at least one offollowing: an SRS resource configuration identifier, a number of SRSports, time domain behavior of SRS resource configuration (e.g., anindication of periodic, semi-persistent, or aperiodic SRS), slot(mini-slot, and/or subframe) level periodicity and/or offset for aperiodic and/or aperiodic SRS resource, a number of OFDM symbols in aSRS resource, starting OFDM symbol of a SRS resource, an SRS bandwidth,a frequency hopping bandwidth, a cyclic shift, and/or an SRS sequenceID.

FIG. 5B shows an example downlink channel mapping and downlink physicalsignals. Downlink transport channels may comprise a Downlink-SharedCHannel (DL-SCH) 511, a Paging CHannel (PCH) 512, and/or a BroadcastCHannel (BCH) 513. A transport channel may be mapped to one or morecorresponding physical channels. A UL-SCH 501 may be mapped to aPhysical Uplink Shared CHannel (PUSCH) 503. A RACH 502 may be mapped toa PRACH 505. A DL-SCH 511 and a PCH 512 may be mapped to a PhysicalDownlink Shared CHannel (PDSCH) 514. A BCH 513 may be mapped to aPhysical Broadcast CHannel (PBCH) 516.

A radio network may comprise one or more downlink and/or uplinktransport channels. The radio network may comprise one or more physicalchannels without a corresponding transport channel The one or morephysical channels may be used for an Uplink Control Information (UCI)509 and/or a Downlink Control Information (DCI) 517. A Physical UplinkControl CHannel (PUCCH) 504 may carry UCI 509 from a wireless device toa base station. A Physical Downlink Control CHannel (PDCCH) 515 maycarry the DCI 517 from a base station to a wireless device. The radionetwork (e.g., NR) may support the UCI 509 multiplexing in the PUSCH503, for example, if the UCI 509 and the PUSCH 503 transmissions maycoincide in a slot (e.g., at least in part). The UCI 509 may comprise atleast one of a CSI, an Acknowledgement (ACK)/Negative Acknowledgement(NACK), and/or a scheduling request. The DCI 517 via the PDCCH 515 mayindicate at least one of following: one or more downlink assignmentsand/or one or more uplink scheduling grants.

In uplink, a wireless device may send (e.g., transmit) one or moreReference Signals (RSs) to a base station. The one or more RSs maycomprise at least one of a Demodulation-RS (DM-RS) 506, a PhaseTracking-RS (PT-RS) 507, and/or a Sounding RS (SRS) 508. In downlink, abase station may send (e.g., transmit, unicast, multicast, and/orbroadcast) one or more RSs to a wireless device. The one or more RSs maycomprise at least one of a Primary Synchronization Signal(PSS)/Secondary Synchronization Signal (SSS) 521, a CSI-RS 522, a DM-RS523, and/or a PT-RS 524.

In a time domain, an SS/PBCH block may comprise one or more OFDM symbols(e.g., 4 OFDM symbols numbered in increasing order from 0 to 3) withinthe SS/PBCH block. An SS/PBCH block may comprise the PSS/SSS 521 and/orthe PBCH 516. In the frequency domain, an SS/PBCH block may comprise oneor more contiguous subcarriers (e.g., 240 contiguous subcarriers withthe subcarriers numbered in increasing order from 0 to 239) within theSS/PBCH block. The PSS/SSS 521 may occupy, for example, 1 OFDM symboland 127 subcarriers. The PBCH 516 may span across, for example, 3 OFDMsymbols and 240 subcarriers. A wireless device may assume that one ormore SS/PBCH blocks transmitted with a same block index may be quasico-located, for example, with respect to Doppler spread, Doppler shift,average gain, average delay, and/or spatial Rx parameters. A wirelessdevice may not assume quasi co-location for other SS/PBCH blocktransmissions. A periodicity of an SS/PBCH block may be configured by aradio network (e.g., by an RRC signaling). One or more time locations inwhich the SS/PBCH block may be sent may be determined by sub-carrierspacing. A wireless device may assume a band-specific sub-carrierspacing for an SS/PBCH block, for example, unless a radio network hasconfigured the wireless device to assume a different sub-carrierspacing.

The downlink CSI-RS 522 may be used for a wireless device to acquirechannel state information. A radio network may support periodic,aperiodic, and/or semi-persistent transmission of the downlink CSI-RS522. A base station may semi-statically configure and/or reconfigure awireless device with periodic transmission of the downlink CSI-RS 522. Aconfigured CSI-RS resources may be activated and/or deactivated. Forsemi-persistent transmission, an activation and/or deactivation of aCSI-RS resource may be triggered dynamically. A CSI-RS configuration maycomprise one or more parameters indicating at least a number of antennaports. A base station may configure a wireless device with 32 ports, orany other number of ports. A base station may semi-statically configurea wireless device with one or more CSI-RS resource sets. One or moreCSI-RS resources may be allocated from one or more CSI-RS resource setsto one or more wireless devices. A base station may semi-staticallyconfigure one or more parameters indicating CSI RS resource mapping, forexample, time-domain location of one or more CSI-RS resources, abandwidth of a CSI-RS resource, and/or a periodicity. A wireless devicemay be configured to use the same OFDM symbols for the downlink CSI-RS522 and the Control Resource Set (CORESET), for example, if the downlinkCSI-RS 522 and the CORESET are spatially quasi co-located and resourceelements associated with the downlink CSI-RS 522 are the outside of PRBsconfigured for the CORESET. A wireless device may be configured to usethe same OFDM symbols for downlink CSI-RS 522 and SSB/PBCH, for example,if the downlink CSI-RS 522 and SSB/PBCH are spatially quasi co-locatedand resource elements associated with the downlink CSI-RS 522 areoutside of the PRBs configured for the SSB/PBCH.

A wireless device may send (e.g., transmit) one or more downlink DM-RSs523 to a base station for channel estimation, for example, for coherentdemodulation of one or more downlink physical channels (e.g., PDSCH514). A radio network may support one or more variable and/orconfigurable DM-RS patterns for data demodulation. At least one downlinkDM-RS configuration may support a front-loaded DM-RS pattern. Afront-loaded DM-RS may be mapped over one or more OFDM symbols (e.g., 1or 2 adjacent OFDM symbols). A base station may semi-staticallyconfigure a wireless device with a maximum number of front-loaded DM-RSsymbols for PDSCH 514. A DM-RS configuration may support one or moreDM-RS ports. A DM-RS configuration may support at least 8 orthogonaldownlink DM-RS ports, for example, for single user-MIMO. ADM-RSconfiguration may support 12 orthogonal downlink DM-RS ports, forexample, for multiuser-MIMO. A radio network may support, for example,at least for CP-OFDM, a common DM-RS structure for DL and UL, wherein aDM-RS location, DM-RS pattern, and/or scrambling sequence may be thesame or different.

Whether or not the downlink PT-RS 524 is present may depend on an RRCconfiguration. A presence of the downlink PT-RS 524 may be wirelessdevice-specifically configured. A presence and/or a pattern of thedownlink PT-RS 524 in a scheduled resource may be wirelessdevice-specifically configured, for example, by a combination of RRCsignaling and/or an association with one or more parameters used forother purposes (e.g., MCS) which may be indicated by the DCI. Ifconfigured, a dynamic presence of the downlink PT-RS 524 may beassociated with one or more DCI parameters comprising at least MCS. Aradio network may support a plurality of PT-RS densities in atime/frequency domain. If present, a frequency domain density may beassociated with at least one configuration of a scheduled bandwidth. Awireless device may assume the same precoding for a DMRS port and aPT-RS port. A number of PT-RS ports may be less than a number of DM-RSports in a scheduled resource. The downlink PT-RS 524 may be confined inthe scheduled time/frequency duration for a wireless device.

FIG. 6 shows an example frame structure, as well as an example framestructure, for a carrier.

A multicarrier OFDM communication system may include one or morecarriers, for example, ranging from 1 to 32 carriers (such as forcarrier aggregation) or ranging from 1 to 64 carriers (such as for dualconnectivity). Different radio frame structures may be supported (e.g.,for FDD and/or for TDD duplex mechanisms). FIG. 6 shows an example framestructure. Downlink and uplink transmissions may be organized into radioframes 601. Radio frame duration may be 10 milliseconds (ms). A 10 msradio frame 601 may be divided into ten equally sized subframes 602,each with a 1 ms duration. Subframe(s) may comprise one or more slots(e.g., slots 603 and 605) depending on subcarrier spacing and/or CPlength. For example, a subframe with 15 kHz, 30 kHz, 60 kHz, 120 kHz,240 kHz and 480 kHz subcarrier spacing may comprise one, two, four,eight, sixteen and thirty-two slots, respectively. In FIG. 6, a subframemay be divided into two equally sized slots 603 with 0.5 ms duration.For example, 10 subframes may be available for downlink transmission and10 subframes may be available for uplink transmissions in a 10 msinterval. Other subframe durations such as, for example, 0.5 ms, 1 ms, 2ms, and 5 ms may be supported. Uplink and downlink transmissions may beseparated in the frequency domain. Slot(s) may include a plurality ofOFDM symbols 604. The number of OFDM symbols 604 in a slot 605 maydepend on the cyclic prefix length. A slot may be 14 OFDM symbols forthe same subcarrier spacing of up to 480 kHz with normal CP. A slot maybe 12 OFDM symbols for the same subcarrier spacing of 60 kHz withextended CP. A slot may comprise downlink, uplink, and/or a downlinkpart and an uplink part, and/or alike.

FIG. 7A shows example sets of OFDM subcarriers. A base station maycommunicate with a wireless device using a carrier having an examplechannel bandwidth 700. Arrow(s) may depict a subcarrier in amulticarrier OFDM system. The OFDM system may use technology such asOFDM technology, SC-FDMA technology, and/or the like. An arrow 701 showsa subcarrier transmitting information symbols. A subcarrier spacing 702,between two contiguous subcarriers in a carrier, may be any one of 15kHz, 30 kHz, 60 kHz, 120 kHz, 240 kHz, or any other frequency. Differentsubcarrier spacing may correspond to different transmissionnumerologies. A transmission numerology may comprise at least: anumerology index; a value of subcarrier spacing; and/or a type of cyclicprefix (CP). A base station may send (e.g., transmit) to and/or receivefrom a wireless device via a number of subcarriers 703 in a carrier. Abandwidth occupied by a number of subcarriers 703 (e.g., transmissionbandwidth) may be smaller than the channel bandwidth 700 of a carrier,for example, due to guard bands 704 and 705. Guard bands 704 and 705 maybe used to reduce interference to and from one or more neighborcarriers. A number of subcarriers (e.g., transmission bandwidth) in acarrier may depend on the channel bandwidth of the carrier and/or thesubcarrier spacing. A transmission bandwidth, for a carrier with a 20MHz channel bandwidth and a 15 kHz subcarrier spacing, may be in numberof 1024 subcarriers.

A base station and a wireless device may communicate with multiplecomponent carriers (CCs), for example, if configured with CA. Differentcomponent carriers may have different bandwidth and/or differentsubcarrier spacing, for example, if CA is supported. A base station maysend (e.g., transmit) a first type of service to a wireless device via afirst component carrier. The base station may send (e.g., transmit) asecond type of service to the wireless device via a second componentcarrier. Different types of services may have different servicerequirements (e.g., data rate, latency, reliability), which may besuitable for transmission via different component carriers havingdifferent subcarrier spacing and/or different bandwidth.

FIG. 7B shows examples of component carriers. A first component carriermay comprise a first number of subcarriers 706 having a first subcarrierspacing 709. A second component carrier may comprise a second number ofsubcarriers 707 having a second subcarrier spacing 710. A thirdcomponent carrier may comprise a third number of subcarriers 708 havinga third subcarrier spacing 711. Carriers in a multicarrier OFDMcommunication system may be contiguous carriers, non-contiguouscarriers, or a combination of both contiguous and non-contiguouscarriers.

FIG. 8 shows an example of OFDM radio resources. A carrier may have atransmission bandwidth 801. A resource grid may be in a structure offrequency domain 802 and time domain 803. A resource grid may comprise afirst number of OFDM symbols in a subframe and a second number ofresource blocks, starting from a common resource block indicated byhigher-layer signaling (e.g., RRC signaling), for a transmissionnumerology and a carrier. In a resource grid, a resource element 805 maycomprise a resource unit that may be identified by a subcarrier indexand a symbol index. A subframe may comprise a first number of OFDMsymbols 807 that may depend on a numerology associated with a carrier. Asubframe may have 14 OFDM symbols for a carrier, for example, if asubcarrier spacing of a numerology of a carrier is 15 kHz. A subframemay have 28 OFDM symbols, for example, if a subcarrier spacing of anumerology is 30 kHz. A subframe may have 56 OFDM symbols, for example,if a subcarrier spacing of a numerology is 60 kHz. A subcarrier spacingof a numerology may comprise any other frequency. A second number ofresource blocks comprised in a resource grid of a carrier may depend ona bandwidth and a numerology of the carrier.

A resource block 806 may comprise 12 subcarriers. Multiple resourceblocks may be grouped into a Resource Block Group (RBG) 804. A size of aRBG may depend on at least one of: a RRC message indicating a RBG sizeconfiguration; a size of a carrier bandwidth; and/or a size of a BWP ofa carrier. A carrier may comprise multiple BWPs. A first BWP of acarrier may have a different frequency location and/or a differentbandwidth from a second BWP of the carrier.

A base station may send (e.g., transmit), to a wireless device, adownlink control information comprising a downlink or uplink resourceblock assignment. A base station may send (e.g., transmit) to and/orreceive from, a wireless device, data packets (e.g., TBs). The datapackets may be scheduled on and transmitted via one or more resourceblocks and one or more slots indicated by parameters in downlink controlinformation and/or RRC message(s). A starting symbol relative to a firstslot of the one or more slots may be indicated to the wireless device. Abase station may send (e.g., transmit) to and/or receive from, awireless device, data packets. The data packets may be scheduled fortransmission on one or more RBGs and in one or more slots.

A base station may send (e.g., transmit), to a wireless device, downlinkcontrol information comprising a downlink assignment. The base stationmay send (e.g., transmit) the DCI via one or more PDCCHs. The downlinkassignment may comprise parameters indicating at least one of amodulation and coding format; resource allocation; and/or HARQinformation related to the DL-SCH. The resource allocation may compriseparameters of resource block allocation; and/or slot allocation. A basestation may allocate (e.g., dynamically) resources to a wireless device,for example, via a Cell-Radio Network Temporary Identifier (C-RNTI) onone or more PDCCHs. The wireless device may monitor the one or morePDCCHs, for example, in order to find possible allocation if itsdownlink reception is enabled. The wireless device may receive one ormore downlink data packets on one or more PDSCH scheduled by the one ormore PDCCHs, for example, if the wireless device successfully detectsthe one or more PDCCHs.

A base station may allocate Configured Scheduling (CS) resources fordown link transmission to a wireless device. The base station may send(e.g., transmit) one or more RRC messages indicating a periodicity ofthe CS grant. The base station may send (e.g., transmit) DCI via a PDCCHaddressed to a Configured Scheduling-RNTI (CS-RNTI) activating the CSresources. The DCI may comprise parameters indicating that the downlinkgrant is a CS grant. The CS grant may be implicitly reused according tothe periodicity defined by the one or more RRC messages. The CS grantmay be implicitly reused, for example, until deactivated.

A base station may send (e.g., transmit), to a wireless device via oneor more PDCCHs, downlink control information comprising an uplink grant.The uplink grant may comprise parameters indicating at least one of amodulation and coding format; a resource allocation; and/or HARQinformation related to the UL-SCH. The resource allocation may compriseparameters of resource block allocation; and/or slot allocation. Thebase station may dynamically allocate resources to the wireless devicevia a C-RNTI on one or more PDCCHs. The wireless device may monitor theone or more PDCCHs, for example, in order to find possible resourceallocation. The wireless device may send (e.g., transmit) one or moreuplink data packets via one or more PUSCH scheduled by the one or morePDCCHs, for example, if the wireless device successfully detects the oneor more PDCCHs.

The base station may allocate CS resources for uplink data transmissionto a wireless device. The base station may transmit one or more RRCmessages indicating a periodicity of the CS grant. The base station maysend (e.g., transmit) DCI via a PDCCH addressed to a CS-RNTI to activatethe CS resources. The DCI may comprise parameters indicating that theuplink grant is a CS grant. The CS grant may be implicitly reusedaccording to the periodicity defined by the one or more RRC message, TheCS grant may be implicitly reused, for example, until deactivated.

A base station may send (e.g., transmit) DCI and/or control signalingvia a PDCCH. The DCI may comprise a format of a plurality of formats.The DCI may comprise downlink and/or uplink scheduling information(e.g., resource allocation information, HARQ related parameters, MCS),request(s) for CSI (e.g., aperiodic CQI reports), request(s) for an SRS,uplink power control commands for one or more cells, one or more timinginformation (e.g., TB transmission/reception timing, HARQ feedbacktiming, etc.), and/or the like. The DCI may indicate an uplink grantcomprising transmission parameters for one or more TBs. The DCI mayindicate a downlink assignment indicating parameters for receiving oneor more TBs. The DCI may be used by the base station to initiate acontention-free RA at the wireless device. The base station may send(e.g., transmit) DCI comprising a slot format indicator (SFI) indicatinga slot format. The base station may send (e.g., transmit) DCI comprisinga preemption indication indicating the PRB(s) and/or OFDM symbol(s) inwhich a wireless device may assume no transmission is intended for thewireless device. The base station may send (e.g., transmit) DCI forgroup power control of the PUCCH, the PUSCH, and/or an SRS. DCI maycorrespond to an RNTI. The wireless device may obtain an RNTI after orin response to completing the initial access (e.g., C-RNTI). The basestation may configure an RNTI for the wireless (e.g., CS-RNTI,TPC-CS-RNTI, TPC-PUCCH-RNTI, TPC-PUSCH-RNTI, TPC-SRS-RNTI, etc.). Thewireless device may determine (e.g., compute) an RNTI (e.g., thewireless device may determine the RA-RNTI based on resources used fortransmission of a preamble). An RNTI may have a pre-configured value(e.g., P-RNTI or SI-RNTI). The wireless device may monitor a groupcommon search space which may be used by the base station for sending(e.g., transmitting) DCIs that are intended for a group of wirelessdevices. A group common DCI may correspond to an RNTI which is commonlyconfigured for a group of wireless devices. The wireless device maymonitor a wireless device-specific search space. A wireless devicespecific DCI may correspond to an RNTI configured for the wirelessdevice.

A communications system (e.g., an NR system) may support a single beamoperation and/or a multi-beam operation. In a multi-beam operation, abase station may perform a downlink beam sweeping to provide coveragefor common control channels and/or downlink SS blocks, which maycomprise at least a PSS, a SSS, and/or PBCH. A wireless device maymeasure quality of a beam pair link using one or more RSs. One or moreSS blocks, or one or more CSI-RS resources (e.g., which may beassociated with a CSI-RS resource index (CRI)), and/or one or moreDM-RSs of a PBCH, may be used as an RS for measuring a quality of a beampair link. The quality of a beam pair link may be based on a referencesignal received power (RSRP) value, a reference signal received quality(RSRQ) value, and/or a CSI value measured on RS resources. The basestation may indicate whether an RS resource, used for measuring a beampair link quality, is quasi-co-located (QCLed) with DM-RSs of a controlchannel. An RS resource and DM-RSs of a control channel may be calledQCLed, for example, if channel characteristics from a transmission on anRS to a wireless device, and that from a transmission on a controlchannel to a wireless device, are similar or the same under a configuredcriterion. In a multi-beam operation, a wireless device may perform anuplink beam sweeping to access a cell.

A wireless device may be configured to monitor a PDCCH on one or morebeam pair links simultaneously, for example, depending on a capabilityof the wireless device. This monitoring may increase robustness againstbeam pair link blocking. A base station may send (e.g., transmit) one ormore messages to configure the wireless device to monitor the PDCCH onone or more beam pair links in different PDCCH OFDM symbols. A basestation may send (e.g., transmit) higher layer signaling (e.g., RRCsignaling) and/or a MAC CE comprising parameters related to the Rx beamsetting of the wireless device for monitoring the PDCCH on one or morebeam pair links. The base station may send (e.g., transmit) anindication of a spatial QCL assumption between an DL RS antenna port(s)(e.g., a cell-specific CSI-RS, a wireless device-specific CSI-RS, an SSblock, and/or a PBCH with or without DM-RSs of the PBCH) and/or DL RSantenna port(s) for demodulation of a DL control channel. Signaling forbeam indication for a PDCCH may comprise MAC CE signaling, RRCsignaling, DCI signaling, and/or specification-transparent and/orimplicit method, and/or any combination of signaling methods.

A base station may indicate spatial QCL parameters between DL RS antennaport(s) and DM-RS antenna port(s) of a DL data channel, for example, forreception of a unicast DL data channel The base station may send (e.g.,transmit) DCI (e.g., downlink grants) comprising information indicatingthe RS antenna port(s). The information may indicate RS antenna port(s)that may be QCL-ed with the DM-RS antenna port(s). A different set ofDM-RS antenna port(s) for a DL data channel may be indicated as QCL witha different set of the RS antenna port(s).

FIG. 9A shows an example of beam sweeping in a DL channel. In anRRC_INACTIVE state or RRC_IDLE state, a wireless device may assume thatSS blocks form an SS burst 940, and an SS burst set 950. The SS burstset 950 may have a given periodicity. A base station 120 may send (e.g.,transmit) SS blocks in multiple beams, together forming a SS burst 940,for example, in a multi-beam operation. One or more SS blocks may besent (e.g., transmitted) on one beam. If multiple SS bursts 940 aretransmitted with multiple beams, SS bursts together may form SS burstset 950.

A wireless device may use CSI-RS for estimating a beam quality of a linkbetween a wireless device and a base station, for example, in the multibeam operation. A beam may be associated with a CSI-RS. A wirelessdevice may (e.g., based on a RSRP measurement on CSI-RS) report a beamindex, which may be indicated in a CRI for downlink beam selectionand/or associated with an RSRP value of a beam. A CSI-RS may be sent(e.g., transmitted) on a CSI-RS resource, which may comprise at leastone of: one or more antenna ports and/or one or more time and/orfrequency radio resources. A CSI-RS resource may be configured in acell-specific way such as by common RRC signaling, or in a wirelessdevice-specific way such as by dedicated RRC signaling and/or L1/L2signaling. Multiple wireless devices covered by a cell may measure acell-specific CSI-RS resource. A dedicated subset of wireless devicescovered by a cell may measure a wireless device-specific CSI-RSresource.

A CSI-RS resource may be sent (e.g., transmitted) periodically, usingaperiodic transmission, or using a multi-shot or semi-persistenttransmission. In a periodic transmission in FIG. 9A, a base station 120may send (e.g., transmit) configured CSI-RS resources 940 periodicallyusing a configured periodicity in a time domain In an aperiodictransmission, a configured CSI-RS resource may be sent (e.g.,transmitted) in a dedicated time slot. In a multi-shot and/orsemi-persistent transmission, a configured CSI-RS resource may be sent(e.g., transmitted) within a configured period. Beams used for CSI-RStransmission may have a different beam width than beams used forSS-blocks transmission.

FIG. 9B shows an example of a beam management procedure, such as a newradio network. The base station 120 and/or the wireless device 110 mayperform a downlink L1/L2 beam management procedure. One or more of thefollowing downlink L1/L2 beam management procedures may be performedwithin one or more wireless devices 110 and one or more base stations120. A P1 procedure 910 may be used to enable the wireless device 110 tomeasure one or more Transmission (Tx) beams associated with the basestation 120, for example, to support a selection of a first set of Txbeams associated with the base station 120 and a first set of Rx beam(s)associated with the wireless device 110. A base station 120 may sweep aset of different Tx beams, for example, for beamforming at a basestation 120 (such as shown in the top row, in a counter-clockwisedirection). A wireless device 110 may sweep a set of different Rx beams,for example, for beamforming at a wireless device 110 (such as shown inthe bottom row, in a clockwise direction). A P2 procedure 920 may beused to enable a wireless device 110 to measure one or more Tx beamsassociated with a base station 120, for example, to possibly change afirst set of Tx beams associated with a base station 120. A P2 procedure920 may be performed on a possibly smaller set of beams (e.g., for beamrefinement) than in the P1 procedure 910. A P2 procedure 920 may be aspecial example of a P1 procedure 910. A P3 procedure 930 may be used toenable a wireless device 110 to measure at least one Tx beam associatedwith a base station 120, for example, to change a first set of Rx beamsassociated with a wireless device 110.

A wireless device 110 may send (e.g., transmit) one or more beammanagement reports to a base station 120. In one or more beam managementreports, a wireless device 110 may indicate one or more beam pairquality parameters comprising one or more of: a beam identification; anRSRP; a Precoding Matrix Indicator (PMI), Channel Quality Indicator(CQI), and/or Rank Indicator (RI) of a subset of configured beams. Basedon one or more beam management reports, the base station 120 may send(e.g., transmit) to a wireless device 110 a signal indicating that oneor more beam pair links are one or more serving beams. The base station120 may send (e.g., transmit) the PDCCH and the PDSCH for a wirelessdevice 110 using one or more serving beams.

A communications network (e.g., a new radio network) may support aBandwidth Adaptation (BA). Receive and/or transmit bandwidths that maybe configured for a wireless device using a BA may not be large. Receiveand/or transmit bandwidth may not be as large as a bandwidth of a cell.Receive and/or transmit bandwidths may be adjustable. A wireless devicemay change receive and/or transmit bandwidths, for example, to reduce(e.g., shrink) the bandwidth(s) at (e.g., during) a period of lowactivity such as to save power. A wireless device may change a locationof receive and/or transmit bandwidths in a frequency domain, forexample, to increase scheduling flexibility. A wireless device maychange a subcarrier spacing, for example, to allow different services.

A Bandwidth Part (BWP) may comprise a subset of a total cell bandwidthof a cell. A base station may configure a wireless device with one ormore BWPs, for example, to achieve a BA. A base station may indicate, toa wireless device, which of the one or more (configured) BWPs is anactive BWP.

FIG. 10 shows an example of BWP configurations. BWPs may be configuredas follows: BWP1 (1010 and 1050) with a width of 40 MHz and subcarrierspacing of 15 kHz; BWP2 (1020 and 1040) with a width of 10 MHz andsubcarrier spacing of 15 kHz; BWP3 1030 with a width of 20 MHz andsubcarrier spacing of 60 kHz. Any number of BWP configurations maycomprise any other width and subcarrier spacing combination.

A wireless device, configured for operation in one or more BWPs of acell, may be configured by one or more higher layers (e.g., RRC layer).The wireless device may be configured for a cell with: a set of one ormore BWPs (e.g., at most four BWPs) for reception (e.g., a DL BWP set)in a DL bandwidth by at least one parameter DL-BWP; and a set of one ormore BWPs (e.g., at most four BWPs) for transmissions (e.g., UL BWP set)in an UL bandwidth by at least one parameter UL-BWP.

A base station may configure a wireless device with one or more UL andDL BWP pairs, for example, to enable BA on the PCell. To enable BA onSCells (e.g., for CA), a base station may configure a wireless device atleast with one or more DL BWPs (e.g., there may be none in an UL).

An initial active DL BWP may comprise at least one of a location andnumber of contiguous PRBs, a subcarrier spacing, or a cyclic prefix, forexample, for a CORESETs for at least one common search space. Foroperation on the PCell, one or more higher layer parameters may indicateat least one initial UL BWP for a RA procedure. If a wireless device isconfigured with a secondary carrier on a primary cell, the wirelessdevice may be configured with an initial BWP for RA procedure on asecondary carrier.

A wireless device may expect that a center frequency for a DL BWP may besame as a center frequency for a UL BWP, for example, for unpairedspectrum operation. A base station may semi-statically configure awireless device for a cell with one or more parameters, for example, fora DL BWP or an UL BWP in a set of one or more DL BWPs or one or more ULBWPs, respectively. The one or more parameters may indicate one or moreof following: a subcarrier spacing; a cyclic prefix; a number ofcontiguous PRBs; an index in the set of one or more DL BWPs and/or oneor more UL BWPs; a link between a DL BWP and an UL BWP from a set ofconfigured DL BWPs and UL BWPs; a DCI detection to a PDSCH receptiontiming; a PDSCH reception to a HARQ-ACK transmission timing value; a DCIdetection to a PUSCH transmission timing value; and/or an offset of afirst PRB of a DL bandwidth or an UL bandwidth, respectively, relativeto a first PRB of a bandwidth.

For a DL BWP in a set of one or more DL BWPs on a PCell, a base stationmay configure a wireless device with one or more control resource setsfor at least one type of common search space and/or one wirelessdevice-specific search space. A base station may not configure awireless device without a common search space on a PCell, or on aPSCell, in an active DL BWP. For an UL BWP in a set of one or more ULBWPs, a base station may configure a wireless device with one or moreresource sets for one or more PUCCH transmissions.

DCI may comprise a BWP indicator field. The BWP indicator field valuemay indicate an active DL BWP, from a configured DL BWP set, for one ormore DL receptions. The BWP indicator field value may indicate an activeUL BWP, from a configured UL BWP set, for one or more UL transmissions.

For a PCell, a base station may semi-statically configure a wirelessdevice with a default DL BWP among configured DL BWPs. If a wirelessdevice is not provided a default DL BWP, a default BWP may be an initialactive DL BWP.

A base station may configure a wireless device with a timer value for aPCell. A wireless device may start a timer (e.g., a BWP inactivitytimer), for example, if a wireless device detects DCI indicating anactive DL BWP, other than a default DL BWP, for a paired spectrumoperation, and/or if a wireless device detects DCI indicating an activeDL BWP or UL BWP, other than a default DL BWP or UL BWP, for an unpairedspectrum operation. The wireless device may increment the timer by aninterval of a first value (e.g., the first value may be 1 millisecond,0.5 milliseconds, or any other time duration), for example, if thewireless device does not detect DCI at (e.g., during) the interval for apaired spectrum operation or for an unpaired spectrum operation. Thetimer may expire at a time that the timer is equal to the timer value. Awireless device may switch to the default DL BWP from an active DL BWP,for example, if the timer expires.

A base station may semi-statically configure a wireless device with oneor more BWPs. A wireless device may switch an active BWP from a firstBWP to a second BWP, for example, after or in response to receiving DCIindicating the second BWP as an active BWP, and/or after or in responseto an expiry of BWP inactivity timer (e.g., the second BWP may be adefault BWP). FIG. 10 shows an example of three BWPs configured, BWP1(1010 and 1050), BWP2 (1020 and 1040), and BWP3 (1030). BWP2 (1020 and1040) may be a default BWP. BWP1 (1010) may be an initial active BWP. Awireless device may switch an active BWP from BWP1 1010 to BWP2 1020,for example, after or in response to an expiry of the BWP inactivitytimer. A wireless device may switch an active BWP from BWP2 1020 to BWP31030, for example, after or in response to receiving DCI indicating BWP31030 as an active BWP. Switching an active BWP from BWP3 1030 to BWP21040 and/or from BWP2 1040 to BWP1 1050 may be after or in response toreceiving DCI indicating an active BWP, and/or after or in response toan expiry of BWP inactivity timer.

Wireless device procedures on a secondary cell may be same as on aprimary cell using the timer value for the secondary cell and thedefault DL BWP for the secondary cell, for example, if a wireless deviceis configured for a secondary cell with a default DL BWP amongconfigured DL BWPs and a timer value. A wireless device may use anindicated DL BWP and an indicated UL BWP on a secondary cell as arespective first active DL BWP and first active UL BWP on a secondarycell or carrier, for example, if a base station configures a wirelessdevice with a first active DL BWP and a first active UL BWP on asecondary cell or carrier.

FIG. 11A and FIG. 11B show packet flows using a multi connectivity(e.g., dual connectivity, multi connectivity, tight interworking, and/orthe like). FIG. 11A shows an example of a protocol structure of awireless device 110 (e.g., UE) with CA and/or multi connectivity. FIG.11B shows an example of a protocol structure of multiple base stationswith CA and/or multi connectivity. The multiple base stations maycomprise a master node, MN 1130 (e.g., a master node, a master basestation, a master gNB, a master eNB, and/or the like) and a secondarynode, SN 1150 (e.g., a secondary node, a secondary base station, asecondary gNB, a secondary eNB, and/or the like). A master node 1130 anda secondary node 1150 may co-work to communicate with a wireless device110.

If multi connectivity is configured for a wireless device 110, thewireless device 110, which may support multiple reception and/ortransmission functions in an RRC connected state, may be configured toutilize radio resources provided by multiple schedulers of a multiplebase stations. Multiple base stations may be inter-connected via anon-ideal or ideal backhaul (e.g., Xn interface, X2 interface, and/orthe like). A base station involved in multi connectivity for a certainwireless device may perform at least one of two different roles: a basestation may act as a master base station or act as a secondary basestation. In multi connectivity, a wireless device may be connected toone master base station and one or more secondary base stations. Amaster base station (e.g., the MN 1130) may provide a master cell group(MCG) comprising a primary cell and/or one or more secondary cells for awireless device (e.g., the wireless device 110). A secondary basestation (e.g., the SN 1150) may provide a secondary cell group (SCG)comprising a primary secondary cell (PSCell) and/or one or moresecondary cells for a wireless device (e.g., the wireless device 110).

In multi connectivity, a radio protocol architecture that a bearer usesmay depend on how a bearer is setup. Three different types of bearersetup options may be supported: an MCG bearer, an SCG bearer, and/or asplit bearer. A wireless device may receive and/or send (e.g., transmit)packets of an MCG bearer via one or more cells of the MCG. A wirelessdevice may receive and/or send (e.g., transmit) packets of an SCG bearervia one or more cells of an SCG. Multi-connectivity may indicate havingat least one bearer configured to use radio resources provided by thesecondary base station. Multi-connectivity may or may not be configuredand/or implemented.

A wireless device (e.g., wireless device 110) may send (e.g., transmit)and/or receive: packets of an MCG bearer via an SDAP layer (e.g., SDAP1110), a PDCP layer (e.g., NR PDCP 1111), an RLC layer (e.g., MN RLC1114), and a MAC layer (e.g., MN MAC 1118); packets of a split bearervia an SDAP layer (e.g., SDAP 1110), a PDCP layer (e.g., NR PDCP 1112),one of a master or secondary RLC layer (e.g., MN RLC 1115, SN RLC 1116),and one of a master or secondary MAC layer (e.g., MN MAC 1118, SN MAC1119); and/or packets of an SCG bearer via an SDAP layer (e.g., SDAP1110), a PDCP layer (e.g., NR PDCP 1113), an RLC layer (e.g., SN RLC1117), and a MAC layer (e.g., MN MAC 1119).

A master base station (e.g., MN 1130) and/or a secondary base station(e.g., SN 1150) may send (e.g., transmit) and/or receive: packets of anMCG bearer via a master or secondary node SDAP layer (e.g., SDAP 1120,SDAP 1140), a master or secondary node PDCP layer (e.g., NR PDCP 1121,NR PDCP 1142), a master node RLC layer (e.g., MN RLC 1124, MN RLC 1125),and a master node MAC layer (e.g., MN MAC 1128); packets of an SCGbearer via a master or secondary node SDAP layer (e.g., SDAP 1120, SDAP1140), a master or secondary node PDCP layer (e.g., NR PDCP 1122, NRPDCP 1143), a secondary node RLC layer (e.g., SN RLC 1146, SN RLC 1147),and a secondary node MAC layer (e.g., SN MAC 1148); packets of a splitbearer via a master or secondary node SDAP layer (e.g., SDAP 1120, SDAP1140), a master or secondary node PDCP layer (e.g., NR PDCP 1123, NRPDCP 1141), a master or secondary node RLC layer (e.g., MN RLC 1126, SNRLC 1144, SN RLC 1145, MN RLC 1127), and a master or secondary node MAClayer (e.g., MN MAC 1128, SN MAC 1148).

In multi connectivity, a wireless device may configure multiple MACentities, such as one MAC entity (e.g., MN MAC 1118) for a master basestation, and other MAC entities (e.g., SN MAC 1119) for a secondary basestation. In multi-connectivity, a configured set of serving cells for awireless device may comprise two subsets: an MCG comprising servingcells of a master base station, and SCGs comprising serving cells of asecondary base station. For an SCG, one or more of followingconfigurations may be used. At least one cell of an SCG may have aconfigured UL CC and at least one cell of a SCG, named as primarysecondary cell (e.g., PSCell, PCell of SCG, PCell), and may beconfigured with PUCCH resources. If an SCG is configured, there may beat least one SCG bearer or one split bearer. After or upon detection ofa physical layer problem or a RA problem on a PSCell, or a number of NRRLC retransmissions has been reached associated with the SCG, or afteror upon detection of an access problem on a PSCell associated with(e.g., during) a SCG addition or an SCG change: an RRC connectionre-establishment procedure may not be triggered, UL transmissionstowards cells of an SCG may be stopped, a master base station may beinformed by a wireless device of a SCG failure type, a DL data transferover a master base station may be maintained (e.g., for a split bearer).An NR RLC acknowledged mode (AM) bearer may be configured for a splitbearer. A PCell and/or a PSCell may not be de-activated. A PSCell may bechanged with a SCG change procedure (e.g., with security key change anda RACH procedure). A bearer type change between a split bearer and a SCGbearer, and/or simultaneous configuration of a SCG and a split bearer,may or may not be supported.

With respect to interactions between a master base station and asecondary base stations for multi-connectivity, one or more of thefollowing may be used. A master base station and/or a secondary basestation may maintain RRM measurement configurations of a wirelessdevice. A master base station may determine (e.g., based on receivedmeasurement reports, traffic conditions, and/or bearer types) to requesta secondary base station to provide additional resources (e.g., servingcells) for a wireless device. After or upon receiving a request from amaster base station, a secondary base station may create and/or modify acontainer that may result in a configuration of additional serving cellsfor a wireless device (or decide that the secondary base station has noresource available to do so). For a wireless device capabilitycoordination, a master base station may provide (e.g., all or a part of)an AS configuration and wireless device capabilities to a secondary basestation. A master base station and a secondary base station may exchangeinformation about a wireless device configuration such as by using RRCcontainers (e.g., inter-node messages) carried via Xn messages. Asecondary base station may initiate a reconfiguration of the secondarybase station existing serving cells (e.g., PUCCH towards the secondarybase station). A secondary base station may decide which cell is aPSCell within a SCG. A master base station may or may not change contentof RRC configurations provided by a secondary base station. A masterbase station may provide recent (and/or the latest) measurement resultsfor SCG cell(s), for example, if an SCG addition and/or an SCG SCelladdition occurs. A master base station and secondary base stations mayreceive information of SFN and/or subframe offset of each other from anOAM and/or via an Xn interface (e.g., for a purpose of DRX alignmentand/or identification of a measurement gap). Dedicated RRC signaling maybe used for sending required system information of a cell as for CA, forexample, if adding a new SCG SCell, except for an SFN acquired from anMIB of a PSCell of a SCG.

FIG. 12 shows an example of a RA procedure. One or more events maytrigger a RA procedure.

For example, one or more events may be at least one of following:initial access from RRC_IDLE, RRC connection re-establishment procedure,handover, DL or UL data arrival in (e.g., during) a state ofRRC_CONNECTED (e.g., if UL synchronization status is non-synchronized),transition from RRC_Inactive, and/or request for other systeminformation. A PDCCH order, a MAC entity, and/or a beam failureindication may initiate a RA procedure.

A RA procedure may comprise or be one of at least a contention based RAprocedure and/or a contention free RA procedure. A contention based RAprocedure may comprise one or more Msg 1 1220 transmissions, one or moreMsg2 1230 transmissions, one or more Msg3 1240 transmissions, andcontention resolution 1250. A contention free RA procedure may compriseone or more Msg 1 1220 transmissions and one or more Msg2 1230transmissions. One or more of Msg 1 1220, Msg 2 1230, Msg 3 1240, and/orcontention resolution 1250 may be transmitted in the same step. Atwo-step RA procedure, for example, may comprise a first transmission(e.g., Msg A) and a second transmission (e.g., Msg B). The firsttransmission (e.g., Msg A) may comprise transmitting, by a wirelessdevice (e.g., wireless device 110) to a base station (e.g., base station120), one or more messages indicating an equivalent and/or similarcontents of Msg1 1220 and Msg3 1240 of a four-step RA procedure. Thesecond transmission (e.g., Msg B) may comprise transmitting, by the basestation (e.g., base station 120) to a wireless device (e.g., wirelessdevice 110) after or in response to the first message, one or moremessages indicating an equivalent and/or similar content of Msg2 1230and contention resolution 1250 of a four-step RA procedure.

A base station may send (e.g., transmit, unicast, multicast, broadcast,etc.), to a wireless device, a RACH configuration 1210 via one or morebeams. The RACH configuration 1210 may comprise one or more parametersindicating at least one of following: an available set of PRACHresources for a transmission of a random access preamble (RAP), initialpreamble power (e.g., RAP initial received target power), an RSRPthreshold for a selection of a SS block and corresponding PRACHresource, a power-ramping factor (e.g., RAP power ramping step), a RAPindex, a maximum number of preamble transmissions, preamble group A andgroup B, a threshold (e.g., message size) to determine the groups ofRAPs, a set of one or more RAPs for a system information request andcorresponding PRACH resource(s) (e.g., if any), a set of one or moreRAPs for a beam failure recovery request and corresponding PRACHresource(s) (e.g., if any), a time window to monitor RAR(s), a timewindow to monitor response(s) on a beam failure recovery request, and/ora contention resolution timer.

The Msg1 1220 may comprise one or more transmissions of a RAP. For acontention based RA procedure, a wireless device may select an SS blockwith an RSRP above the RSRP threshold. If RAPs group B exists, awireless device may select one or more RAPs from a group A or a group B,for example, depending on a potential Msg3 1240 size. If a RAPs group Bdoes not exist, a wireless device may select the one or more RAPs from agroup A. A wireless device may select a RAP index randomly (e.g., withequal probability or a normal distribution) from one or more RAPsassociated with a selected group. If a base station semi-staticallyconfigures a wireless device with an association between RAPs and SSblocks, the wireless device may select a RAP index randomly with equalprobability from one or more RAPs associated with a selected SS blockand a selected group.

A wireless device may initiate a contention free RA procedure, forexample, based on a beam failure indication from a lower layer. A basestation may semi-statically configure a wireless device with one or morecontention free PRACH resources for a beam failure recovery requestassociated with at least one of SS blocks and/or CSI-RSs. A wirelessdevice may select a RAP index corresponding to a selected SS block or aCSI-RS from a set of one or more RAPs for a beam failure recoveryrequest, for example, if at least one of the SS blocks with an RSRPabove a first RSRP threshold among associated SS blocks is available,and/or if at least one of CSI-RSs with a RSRP above a second RSRPthreshold among associated CSI-RSs is available.

A wireless device may receive, from a base station, a RAP index viaPDCCH or RRC for a contention free RA procedure. The wireless device mayselect a RAP index, for example, if a base station does not configure awireless device with at least one contention free PRACH resourceassociated with SS blocks or CSI-RS. The wireless device may select theat least one SS block and/or select a RAP corresponding to the at leastone SS block, for example, if a base station configures the wirelessdevice with one or more contention free PRACH resources associated withSS blocks and/or if at least one SS block with a RSRP above a first RSRPthreshold among associated SS blocks is available. The wireless devicemay select the at least one CSI-RS and/or select a RAP corresponding tothe at least one CSI-RS, for example, if a base station configures awireless device with one or more contention free PRACH resourcesassociated with CSI-RSs and/or if at least one CSI-RS with a RSRP abovea second RSPR threshold among the associated CSI-RSs is available.

A wireless device may perform one or more Msg1 1220 transmissions, forexample, by sending (e.g., transmitting) the selected RAP. The wirelessdevice may determine a PRACH occasion from one or more PRACH occasionscorresponding to a selected SS block, for example, if the wirelessdevice selects an SS block and is configured with an association betweenone or more PRACH occasions and/or one or more SS blocks. The wirelessdevice may determine a PRACH occasion from one or more PRACH occasionscorresponding to a selected CSI-RS, for example, if the wireless deviceselects a CSI-RS and is configured with an association between one ormore PRACH occasions and one or more CSI-RSs. The wireless device maysend (e.g., transmit), to a base station, a selected RAP via a selectedPRACH occasions. The wireless device may determine a transmit power fora transmission of a selected RAP at least based on an initial preamblepower and a power-ramping factor. The wireless device may determine anRA-RNTI associated with a selected PRACH occasion in which a selectedRAP is sent (e.g., transmitted). The wireless device may not determinean RA-RNTI for a beam failure recovery request. The wireless device maydetermine an RA-RNTI at least based on an index of a first OFDM symbol,an index of a first slot of a selected PRACH occasions, and/or an uplinkcarrier index for a transmission of Msg1 1220.

A wireless device may receive, from a base station, a RAR, Msg 2 1230.The wireless device may start a time window (e.g., ra-ResponseWindow) tomonitor a RAR. For a beam failure recovery procedure, the base stationmay configure the wireless device with a different time window (e.g.,bfr-ResponseWindow) to monitor response to on a beam failure recoveryrequest. The wireless device may start a time window (e.g.,ra-ResponseWindow or bfr-ResponseWindow) at a start of a first PDCCHoccasion, for example, after a fixed duration of one or more symbolsfrom an end of a preamble transmission. If the wireless device sends(e.g., transmits) multiple preambles, the wireless device may start atime window at a start of a first PDCCH occasion after a fixed durationof one or more symbols from an end of a first preamble transmission. Thewireless device may monitor a PDCCH of a cell for at least one RARidentified by a RA-RNTI, or for at least one response to a beam failurerecovery request identified by a C-RNTI, at a time that a timer for atime window is running

A wireless device may determine that a reception of RAR is successful,for example, if at least one RAR comprises a random access preambleidentifier (RAPID) corresponding to a RAP sent (e.g., transmitted) bythe wireless device. The wireless device may determine that thecontention free RA procedure is successfully completed, for example, ifa reception of a RAR is successful. The wireless device may determinethat a contention free RA procedure is successfully complete, forexample, if a contention free RA procedure is triggered for a beamfailure recovery request and if a PDCCH transmission is addressed to aC-RNTI. The wireless device may determine that the RA procedure issuccessfully completed, and may indicate a reception of anacknowledgement for a system information request to upper layers, forexample, if at least one RAR comprises a RAPID. The wireless device maystop sending (e.g., transmitting) remaining preambles (if any) after orin response to a successful reception of a corresponding RAR, forexample, if the wireless device has signaled multiple preambletransmissions.

The wireless device may perform one or more Msg 3 1240 transmissions,for example, after or in response to a successful reception of RAR(e.g., for a contention based RA procedure). The wireless device mayadjust an uplink transmission timing, for example, based on a timingadvanced command indicated by a RAR. The wireless device may send (e.g.,transmit) one or more TBs, for example, based on an uplink grantindicated by a RAR. Subcarrier spacing for PUSCH transmission for Msg31240 may be provided by at least one higher layer (e.g., RRC) parameter.The wireless device may send (e.g., transmit) a RAP via a PRACH, andMsg3 1240 via PUSCH, on the same cell. A base station may indicate an ULBWP for a PUSCH transmission of Msg3 1240 via system information block.The wireless device may use HARQ for a retransmission of Msg 3 1240.

Multiple wireless devices may perform Msg 1 1220, for example, bysending (e.g., transmitting) the same preamble to a base station. Themultiple wireless devices may receive, from the base station, the sameRAR comprising an identity (e.g., TC-RNTI). Contention resolution (e.g.,comprising the wireless device 110 receiving contention resolution 1250)may be used to increase the likelihood that a wireless device does notincorrectly use an identity of another wireless device. The contentionresolution 1250 may be based on, for example, a C-RNTI on a PDCCH,and/or a wireless device contention resolution identity on a DL-SCH. Ifa base station assigns a C-RNTI to a wireless device, the wirelessdevice may perform contention resolution (e.g., comprising receivingcontention resolution 1250), for example, based on a reception of aPDCCH transmission that is addressed to the C-RNTI. The wireless devicemay determine that contention resolution is successful, and/or that a RAprocedure is successfully completed, for example, after or in responseto detecting a C-RNTI on a PDCCH. If a wireless device has no validC-RNTI, a contention resolution may be addressed by using a TC-RNTI. Ifa MAC PDU is successfully decoded and a MAC PDU comprises a wirelessdevice contention resolution identity MAC CE that matches or otherwisecorresponds with the CCCH SDU sent (e.g., transmitted) in Msg3 1250, thewireless device may determine that the contention resolution (e.g.,comprising contention resolution 1250) is successful and/or the wirelessdevice may determine that the RA procedure is successfully completed.

RA procedures may be used to establish communications between a wirelessdevice and a base station associated with a cell. A four-step RAprocedure (e.g., such as shown in FIG. 12 and described above) may havean associated latency. The associated latency for the four-step RAprocedure may be a minimum of a quantity (e.g., fourteen or any otherquantity) of transmission time intervals (TTIs). A TTI may be anytransmission time interval or other time duration. A minimum latency offourteen TTIs may comprise, for example, three TTIs after a message fromstep 1 1220 of a four-step RA procedure, one TTI for a message from step2 1230 of a four-step RA procedure, five TTIs after the message fromstep 2, one TTI for a message from step 3 1240 of a four-step RAprocedure, three TTIs after the message from step 3, and one TTI for amessage from step 4 1250 of a four-step procedure (e.g.,3+1+5+1+3+1=14). The minimum latency may comprise any quantity of TTIs.Any of the above-references messages may comprise any quantity of TTIs.Reducing the number of steps in an RA procedure may reduce latency. Afour-step RA procedure may be reduced to a two-step RA procedure, forexample, by using parallel transmissions. A two-step RA procedure mayhave an associated latency. The associated latency for a two-step RAprocedure may be a minimum of four TTIs and which may be less than anassociated latency for a four-step RA procedure. A minimum latency offour TTIs may be a minimum of a quantity (e.g., four or any otherquantity) of TTIs. A minimum latency of four TTIs may comprise, forexample, three TTIs after a message from step 1 of a two-step RAprocedure, and one TTI for a message from step 2 of a two-step RAprocedure.

FIG. 13 shows an example structure for MAC entities. A wireless devicemay be configured to operate in a multi-connectivity mode. A wirelessdevice in RRC_CONNECTED with multiple Rx/Tx may be configured to utilizeradio resources provided by multiple schedulers that may be located in aplurality of base stations. The plurality of base stations may beconnected via a non-ideal or ideal backhaul over the Xn interface. Abase station in a plurality of base stations may act as a master basestation or as a secondary base station. A wireless device may beconnected to and/or in communication with, for example, one master basestation and one or more secondary base stations. A wireless device maybe configured with multiple MAC entities, for example, one MAC entityfor a master base station, and one or more other MAC entities forsecondary base station(s). A configured set of serving cells for awireless device may comprise two subsets: an MCG comprising servingcells of a master base station, and one or more SCGs comprising servingcells of a secondary base station(s). FIG. 13 shows an example structurefor MAC entities in which a MCG and a SCG are configured for a wirelessdevice.

At least one cell in a SCG may have a configured UL CC. A cell of the atleast one cell may comprise a PSCell or a PCell of a SCG, or a PCell. APSCell may be configured with PUCCH resources. There may be at least oneSCG bearer, or one split bearer, for a SCG that is configured. After orupon detection of a physical layer problem or a RA problem on a PSCell,after or upon reaching a number of RLC retransmissions associated withthe SCG, and/or after or upon detection of an access problem on a PSCellassociated with (e.g., during) a SCG addition or a SCG change: an RRCconnection re-establishment procedure may not be triggered, ULtransmissions towards cells of a SCG may be stopped, and/or a masterbase station may be informed by a wireless device of a SCG failure typeand DL data transfer over a master base station may be maintained.

A MAC sublayer may provide services such as data transfer and radioresource allocation to upper layers (e.g., 1310 or 1320). A MAC sublayermay comprise a plurality of MAC entities (e.g., 1350 and 1360). A MACsublayer may provide data transfer services on logical channels. Toaccommodate different kinds of data transfer services, multiple types oflogical channels may be defined. A logical channel may support transferof a particular type of information. A logical channel type may bedefined by what type of information (e.g., control or data) istransferred. BCCH, PCCH, CCCH and/or DCCH may be control channels, andDTCH may be a traffic channel. A first MAC entity (e.g., 1310) mayprovide services on PCCH, BCCH, CCCH, DCCH, DTCH, and/or MAC controlelements. A second MAC entity (e.g., 1320) may provide services on BCCH,DCCH, DTCH, and/or MAC control elements.

A MAC sublayer may expect from a physical layer (e.g., 1330 or 1340)services such as data transfer services, signaling of HARQ feedback,and/or signaling of scheduling request or measurements (e.g., CQI). Indual connectivity, two MAC entities may be configured for a wirelessdevice: one for a MCG and one for a SCG. A MAC entity of a wirelessdevice may handle a plurality of transport channels. A first MAC entitymay handle first transport channels comprising a PCCH of a MCG, a firstBCH of the MCG, one or more first DL-SCHs of the MCG, one or more firstUL-SCHs of the MCG, and/or one or more first RACHs of the MCG. A secondMAC entity may handle second transport channels comprising a second BCHof a SCG, one or more second DL-SCHs of the SCG, one or more secondUL-SCHs of the SCG, and/or one or more second RACHs of the SCG.

If a MAC entity is configured with one or more SCells, there may bemultiple DL-SCHs, multiple UL-SCHs, and/or multiple RACHs per MACentity. There may be one DL-SCH and/or one UL-SCH on an SpCell. Theremay be one DL-SCH, zero or one UL-SCH, and/or zero or one RACH for anSCell. A DL-SCH may support receptions using different numerologiesand/or TTI duration within a MAC entity. A UL-SCH may supporttransmissions using different numerologies and/or TTI duration withinthe MAC entity.

A MAC sublayer may support different functions. The MAC sublayer maycontrol these functions with a control (e.g., Control 1355 and/orControl 1365) element. Functions performed by a MAC entity may compriseone or more of: mapping between logical channels and transport channels(e.g., in uplink or downlink), multiplexing (e.g., (De-) Multiplexing1352 and/or (De-) Multiplexing 1362) of MAC SDUs from one or differentlogical channels onto TBs to be delivered to the physical layer ontransport channels (e.g., in uplink), demultiplexing (e.g., (De-)Multiplexing 1352 and/or (De-) Multiplexing 1362) of MAC SDUs to one ordifferent logical channels from TBs delivered from the physical layer ontransport channels (e.g., in downlink), scheduling information reporting(e.g., in uplink), error correction through HARQ in uplink and/ordownlink (e.g., 1363), and logical channel prioritization in uplink(e.g., Logical Channel Prioritization 1351 and/or Logical ChannelPrioritization 1361). A MAC entity may handle a RA process (e.g., RandomAccess Control 1354 and/or Random Access Control 1364).

FIG. 14 shows an example of a RAN architecture comprising one or morebase stations. A protocol stack (e.g., RRC, SDAP, PDCP, RLC, MAC, and/orPHY) may be supported at a node. A base station (e.g., gNB 120A and/or120B) may comprise a base station central unit (CU) (e.g., gNB-CU 1420Aor 1420B) and at least one base station distributed unit (DU) (e.g.,gNB-DU 1430A, 1430B, 1430C, and/or 1430D), for example, if a functionalsplit is configured. Upper protocol layers of a base station may belocated in a base station CU, and lower layers of the base station maybe located in the base station DUs. An F1 interface (e.g., CU-DUinterface) connecting a base station CU and base station DUs may be anideal or non-ideal backhaul. F1-C may provide a control plane connectionover an F1 interface, and F1-U may provide a user plane connection overthe F1 interface. An Xn interface may be configured between base stationCUs.

A base station CU may comprise an RRC function, an SDAP layer, and/or aPDCP layer. Base station DUs may comprise an RLC layer, a MAC layer,and/or a PHY layer. Various functional split options between a basestation CU and base station DUs may be possible, for example, bylocating different combinations of upper protocol layers (e.g., RANfunctions) in a base station CU and different combinations of lowerprotocol layers (e.g., RAN functions) in base station DUs. A functionalsplit may support flexibility to move protocol layers between a basestation CU and base station DUs, for example, depending on servicerequirements and/or network environments.

Functional split options may be configured per base station, per basestation CU, per base station DU, per wireless device, per bearer, perslice, and/or with other granularities. In a per base station CU split,a base station CU may have a fixed split option, and base station DUsmay be configured to match a split option of a base station CU. In a perbase station DU split, a base station DU may be configured with adifferent split option, and a base station CU may provide differentsplit options for different base station DUs. In a per wireless devicesplit, a base station (e.g., a base station CU and at least one basestation DUs) may provide different split options for different wirelessdevices. In a per bearer split, different split options may be utilizedfor different bearers. In a per slice splice, different split optionsmay be used for different slices.

FIG. 15 shows example RRC state transitions of a wireless device. Awireless device may be in at least one RRC state among an RRC connectedstate (e.g., RRC Connected 1530, RRC_Connected, etc.), an RRC idle state(e.g., RRC Idle 1510, RRC_Idle, etc.), and/or an RRC inactive state(e.g., RRC Inactive 1520, RRC_Inactive, etc.). In an RRC connectedstate, a wireless device may have at least one RRC connection with atleast one base station (e.g., gNB and/or eNB), which may have a contextof the wireless device (e.g., UE context). A wireless device context(e.g., UE context) may comprise at least one of an access stratumcontext, one or more radio link configuration parameters, bearer (e.g.,data radio bearer (DRB), signaling radio bearer (SRB), logical channel,QoS flow, PDU session, and/or the like) configuration information,security information, PHY/MAC/RLC/PDCP/SDAP layer configurationinformation, and/or the like configuration information for a wirelessdevice. In an RRC idle state, a wireless device may not have an RRCconnection with a base station, and a context of the wireless device maynot be stored in a base station. In an RRC inactive state, a wirelessdevice may not have an RRC connection with a base station. A context ofa wireless device may be stored in a base station, which may comprise ananchor base station (e.g., a last serving base station).

A wireless device may transition an RRC state (e.g., UE RRC state)between an RRC idle state and an RRC connected state in both ways (e.g.,connection release 1540 or connection establishment 1550; and/orconnection reestablishment) and/or between an RRC inactive state and anRRC connected state in both ways (e.g., connection inactivation 1570 orconnection resume 1580). A wireless device may transition its RRC statefrom an RRC inactive state to an RRC idle state (e.g., connectionrelease 1560).

An anchor base station may be a base station that may keep a context ofa wireless device (e.g., UE context) at least at (e.g., during) a timeperiod that the wireless device stays in a RAN notification area (RNA)of an anchor base station, and/or at (e.g., during) a time period thatthe wireless device stays in an RRC inactive state. An anchor basestation may comprise a base station that a wireless device in an RRCinactive state was most recently connected to in a latest RRC connectedstate, and/or a base station in which a wireless device most recentlyperformed an RNA update procedure. An RNA may comprise one or more cellsoperated by one or more base stations. A base station may belong to oneor more RNAs. A cell may belong to one or more RNAs.

A wireless device may transition, in a base station, an RRC state (e.g.,UE RRC state) from an RRC connected state to an RRC inactive state. Thewireless device may receive RNA information from the base station. RNAinformation may comprise at least one of an RNA identifier, one or morecell identifiers of one or more cells of an RNA, a base stationidentifier, an IP address of the base station, an AS context identifierof the wireless device, a resume identifier, and/or the like.

An anchor base station may broadcast a message (e.g., RAN pagingmessage) to base stations of an RNA to reach to a wireless device in anRRC inactive state. The base stations receiving the message from theanchor base station may broadcast and/or multicast another message(e.g., paging message) to wireless devices in their coverage area, cellcoverage area, and/or beam coverage area associated with the RNA via anair interface.

A wireless device may perform an RNA update (RNAU) procedure, forexample, if the wireless device is in an RRC inactive state and movesinto a new RNA. The RNAU procedure may comprise a RA procedure by thewireless device and/or a context retrieve procedure (e.g., UE contextretrieve). A context retrieve procedure may comprise: receiving, by abase station from a wireless device, a RAP; and requesting and/orreceiving (e.g., fetching), by a base station, a context of the wirelessdevice (e.g., UE context) from an old anchor base station. Therequesting and/or receiving (e.g., fetching) may comprise: sending aretrieve context request message (e.g., UE context request message)comprising a resume identifier to the old anchor base station andreceiving a retrieve context response message comprising the context ofthe wireless device from the old anchor base station.

A wireless device in an RRC inactive state may select a cell to camp onbased on at least a measurement result for one or more cells, a cell inwhich a wireless device may monitor an RNA paging message, and/or a corenetwork paging message from a base station. A wireless device in an RRCinactive state may select a cell to perform a RA procedure to resume anRRC connection and/or to send (e.g., transmit) one or more packets to abase station (e.g., to a network). The wireless device may initiate a RAprocedure to perform an RNA update procedure, for example, if a cellselected belongs to a different RNA from an RNA for the wireless devicein an RRC inactive state. The wireless device may initiate a RAprocedure to send (e.g., transmit) one or more packets to a base stationof a cell that the wireless device selects, for example, if the wirelessdevice is in an RRC inactive state and has one or more packets (e.g., ina buffer) to send (e.g., transmit) to a network. A RA procedure may beperformed with two messages (e.g., 2-stage or 2-step random access)and/or four messages (e.g., 4-stage or 4-step random access) between thewireless device and the base station.

A base station receiving one or more uplink packets from a wirelessdevice in an RRC inactive state may request and/or receive (e.g., fetch)a context of a wireless device (e.g., UE context), for example, bysending (e.g., transmitting) a retrieve context request message for thewireless device to an anchor base station of the wireless device basedon at least one of an AS context identifier, an RNA identifier, a basestation identifier, a resume identifier, and/or a cell identifierreceived from the wireless device. A base station may send (e.g.,transmit) a path switch request for a wireless device to a core networkentity (e.g., AMF, MME, and/or the like), for example, after or inresponse to requesting and/or receiving (e.g., fetching) a context. Acore network entity may update a downlink tunnel endpoint identifier forone or more bearers established for the wireless device between a userplane core network entity (e.g., UPF, S-GW, and/or the like) and a RANnode (e.g., the base station), such as by changing a downlink tunnelendpoint identifier from an address of the anchor base station to anaddress of the base station).

A base station may communicate with a wireless device via a wirelessnetwork using one or more technologies, such as new radio technologies(e.g., NR, 5G, etc.). The one or more radio technologies may comprise atleast one of: multiple technologies related to physical layer; multipletechnologies related to medium access control layer; and/or multipletechnologies related to radio resource control layer Enhancing the oneor more radio technologies may improve performance of a wirelessnetwork. System throughput, and/or data rate of transmission, may beincreased. Battery consumption of a wireless device may be reduced.Latency of data transmission between a base station and a wirelessdevice may be improved. Network coverage of a wireless network may beimproved. Transmission efficiency of a wireless network may be improved.

FIG. 16 shows an example of a two-step RA procedure. The procedure maycomprise an uplink (UL) transmission of a two-step Msg1 1620, forexample, based on a two-step RACH configuration 1610 from a basestation. The two-step Msg1 1620 may be referred to as message A (e.g.,Msg A). The transmission may comprise a RAP transmission 1630 and one ormore TBs for transmission 1640. The UL transmission may be followed by adownlink (DL) transmission of a two-step Msg2 1650 that may comprise aresponse (e.g., random access response (RAR)) corresponding to theuplink transmission. The two-step Msg2 1650 may be referred to as amessage B (e.g., Msg B). The response may comprise contention resolutioninformation.

A wireless device may receive (e.g., from a base station) one or moreRRC messages to configure one or more parameters of a two step RACHconfiguration 1610. The one or more RRC messages may be broadcasted ormulticasted to one or more wireless devices. The one or more RRCmessages may be wireless device-specific messages (e.g., a dedicated RRCmessage sent (e.g., transmitted) to a wireless device indicating RRCINACTIVE 1520 or RRC CONNECTED 1530). The one or more RRC messages maycomprise parameters for sending (e.g., transmitting) a two-step Msg11620. The parameters may indicate one or more of following: PRACHresource allocation, preamble format, SSB information (e.g., totalnumber of SSBs, downlink resource allocation of SSB transmission,transmission power of SSB transmission, and/or other information),and/or uplink radio resources for one or more TB transmissions.

A base station may receive (e.g., from a wireless device via a cell), aRAP transmission for UL time alignment and/or one or more TBs (e.g.,delay-sensitive data, wireless device ID, security information, deviceinformation such as IMSI, and/or other information), for example, in theUL transmission of a two-step RA procedure. A base station may send(e.g., transmit) a two-step Msg2 1650 (e.g., an RAR), for example, inthe DL transmission of the two-step RA procedure. The two-step Msg2 1650(e.g., an RAR) may comprise at least one of following: a timing advancecommand indicating the TA value, a power control command, an UL grant(e.g., radio resource assignment, and/or MCS), a wireless device ID forcontention resolution, an RNTI (e.g., C-RNTI or TC-RNTI), and/or otherinformation. The two-step Msg2 1650 (e.g., an RAR) may comprise apreamble identifier corresponding to the preamble 1630, a positive ornegative acknowledgement of a reception of the one or more TBs 1640,and/or an indication of a successful decoding of the one or more TBs1640. A two-step RA procedure may reduce RA latency compared with afour-step RA procedure for example, by integrating a RAP transmission(such as a process to obtain a timing advance value) with one or more TBtransmissions.

A base station may receive (e.g., from a wireless device via a cell) anRAP in parallel with one or more TBs, for example, in the ULtransmission of a two-step RA procedure. The wireless device may acquireone or more configuration parameters for the UL transmission before thewireless device starts a two-step RA procedure (e.g., at step 1610 inFIG. 16). The one or more configuration parameters may indicate one ormore of following: PRACH resource allocation, preamble format, SSBinformation (e.g., a number of transmitting SSBs, downlink resourceallocation of SSB transmissions, transmission power of SSB transmission,and/or other information), uplink radio resources (e.g., in terms oftime, frequency, code/sequence/signature) for one or more TBtransmissions, and/or power control parameters of one or more TBtransmissions (e.g., cell and/or wireless device specific poweradjustments used for determining (e.g., calculating) received targetpower, inter-cell interference control parameter that may be used as ascaling factor of pathloss measurement, reference signal power todetermine (e.g., calculate for) pathloss measurement, and/or one or moremargins).

A wireless device may generate an RAP. A two-step RACH configuration maycomprise RAP generating parameters (e.g., a root sequence) that may beemployed by the wireless device to generate an RAP. The wireless devicemay use the RAP generating parameters to generate one or more candidatepreambles and may randomly select one of the candidate preambles as theRAP. The RAP generating parameters may be SSB-specific and/orcell-specific. RAP generating parameters for a first SSB may bedifferent from or the same as RAP generating parameters for a secondSSB. A base station may send (e.g., transmit) a control message (e.g.,RRC message for a handover, and/or a PDCCH order for a secondary celladdition) that comprises a preamble index indicating an RAP dedicated toa wireless device to initiate a two-step RA procedure. The one or morecandidate preambles may be organized into groups that may indicate anamount of data for transmission. The amount of data may indicate one ormore TBs that remain in the buffer. Each of the groups may be associatedwith a range of data size. A first group of the groups may comprise RAPsindicated for small data transmissions. A second group may comprise RAPsindicated for larger data transmissions. A wireless device may determinea group of RAPs by comparing one or more thresholds and an amount ofdata, for example, based on an RRC message comprising one or morethresholds (e.g., transmitted by a based station). The wireless devicemay be able to indicate a size of data the wireless device may have fortransmission, for example, by sending (e.g., transmitting) an RAP from aspecific group of RAPs.

In a two-step RA procedure, a wireless device may send (e.g., transmit)a RAP via a RACH resource indicated by a two-step RACH configuration.The wireless device may send (e.g., transmit) one or more TBs via an ULradio resource indicated by a two-step RACH configuration. Thetransmission of the RAP may be overlapped in time (e.g., partially orentirely) with the transmission of the one or more TBs. The two-stepRACH configuration may indicate a portion of overlapping of radioresources between the RAP and one or more TB transmissions. The two-stepRACH configuration may indicate one or more UL radio resourcesassociated with one or more RAPs (and/or RAP groups) and/or the RACHresource. A wireless device may determine at least one UL radio resourcein which the wireless device may send (e.g., transmit) one or more TBsas a part of a two-step RACH procedure, for example, based on aselection of an RAP, an RAP group, and/or an RACH resource The one ormore UL radio resources may be indicated based on a frame structure(such as shown in FIG. 6), and/or OFDM radio structure (such as shown inFIG. 8), The indication may be with respect to an SFN (e.g., SFN=0),slot number, and/or OFDM symbol number for a time domain radio resource,and/or with respect to a subcarrier number, a number of resourceelements, a number of resource blocks, RBG number, and/or frequencyindex for a frequency domain radio resource. The one or more UL radioresources may be indicated based on a time offset and/or a frequencyoffset with respect to one or more RACH resources of a selected RAP. TheUL transmissions may occur (e.g., in the same subframe orslot/mini-slot) in consecutive subframes (or slot/mini-slot), or in thesame burst.

A PRACH resource and one or more associated UL radio resources for atwo-step Msg1 may be allocated with a time offset and/or frequencyoffset, for example, such as provided (e.g., configured, determined,indicated, etc.) by RRC messages (e.g., as a part of RACH config.)and/or predefined (e.g., as a mapping table).

FIG. 17A, FIG. 17B, and FIG. 17C show examples of radio resourceallocations of a random access resource (e.g., PRACH) 1702 and one ormore associated radio resources 1704. UL radio resources may be based ona time offset 1706, a frequency offset 1708, and a combination of a timeoffset 1706 and a frequency offset 1708, respectively. FIG. 17A, FIG.17B, and FIG. 17C comprise a PRACH resource 1702 and a UL radio resource1704 that are associated with a single SSB transmission. The PRACHresource 1702 and/or the UL radio resource 1704 may be associated with afirst SSB transmission of one or more SSB transmissions.

A base station may acquire a UL transmission timing, for example, bydetecting an RAP sent (e.g., transmitted) PRACH resource 1702 based onthe time offset 1706 and/or the frequency offset 1708. A base stationmay detect and/or decode one or more TBs sent (e.g., transmitted) viaone or more associated UL radio resources 1704, for example, based onthe UL transmission timing acquired from the RAP detection. A basestation may send (e.g., transmit) one or more SSBs. Each of the one ormore SSBs may have one or more associated PRACH resources 1702 and/or ULradio resources 1704 provided by (e.g., configured by, indicated by,etc.) a two-step RACH configuration. A wireless device may measure oneor more SSBs. The wireless device may select at least one SSB, forexample, based on measured received signal strength (and/or based onother selection rule). The wireless device may respectively send (e.g.,transmit) an RAP and/or one or more TBs: via PRACH resources 1702associated with the at least one SSB, and/or via UL radio resources 1704associated with the PRACH resources 1702 and/or UL radio resources 1704associated with the at least one SSB.

A base station may use the RAP transmission to adjust UL transmissiontime for a cell and/or to aid in channel estimation for one or more TBs.A portion of the UL transmission for one or more TBs in a two-step RACHprocedure may comprise one or more of: a wireless device ID, a C-RNTI, aservice request such as buffer state reporting (e.g., a buffer statusreport) (BSR), a user data packet, and/or other information. A wirelessdevice in an RRC CONNECTED state may use a C-RNTI as an identifier ofthe wireless device (e.g., a wireless device ID). A wireless device inan RRC INACTIVE state may use a C-RNTI (if available), a resume ID,and/or a short MAC-ID as an identifier of the wireless device. Awireless device in an RRC IDLE state may use a C-RNTI (if available), aresume ID, a short MACID, an IMSI (International Mobile SubscriberIdentifier), a T-IMSI (Temporary-IMSI), and/or a random number as anidentifier of the wireless device.

In a two-step RACH procedure, the UL transmission may comprise one ormore TBs that may be sent (e.g., transmitted) in one or more ways. Firstresource(s) allocated for one or more TBs may be multiplexed with secondresource(s) allocated for an RAP transmission in time and/or frequencydomains. One or more resources may be configured (e.g., by a basestation) to be reserved for the UL transmission that may be indicated toa wireless device before the UL transmission. A base station may send(e.g., transmit) in a two-step Msg2 1650 (e.g., an RAR) that maycomprise a contention resolution message and/or an acknowledgement (ACKor NACK) message of the one or more TBs, for example, based on one ormore TBs sent (e.g., transmitted) by a wireless device in a two-stepMsg1 1620 of a two-step RA procedure. A wireless device may send (e.g.,transmit) one or more second TBs after the reception of an RAR. Thewireless device may send (e.g., transmit) an indicator, such as bufferstate reporting, in a two-step Msg1 1620 of a two-step RA procedure. Theindicator may indicate to a base station an amount of data the wirelessdevice to send (e.g., transmit) and/or an amount of data remains in abuffer. The base station may determine a UL grant based on theindicator. The wireless device may receive (e.g., from a base station)the UL grant to via an RAR.

A wireless device may receive two separate responses in a two-step/RAprocedure: a first response for RAP transmission, and a second responsefor one or more TB transmission. A wireless device may monitor orcontinue to monitor a common search space to detect the first responsewith a random access RNTI generated based on time and frequency indicesof a PRACH resource in which the wireless device may send (e.g.,transmit) an RAP. A wireless device may monitor or continue to monitor acommon search space and/or a wireless device specific search space todetect the second response. The wireless device may employ a C-RNTI(e.g., if configured) and/or a random access RNTI generated based on oneor more time indicies and/or one or more frequency indices of a PRACHresource in which the wireless device may send (e.g., transmit) an RAP,for example, to detect the second response. The wireless device-specificsearch space may be predefined and/or configured by an RRC message.

One or more events may trigger a two-step RA procedure. The one or moreevents may be one or more of: an initial access from RRC_IDLE, a RRCconnection re-establishment procedure, a handover, a DL or a UL dataarrival during RRC_CONNECTED if UL synchronization status isnon-synchronized, a transition from RRC_Inactive, a beam failurerecovery procedure, and/or a request for other system information. APDCCH order, a wireless device (e.g., a MAC entity of a wirelessdevice), and/or a beam failure indication may initiate a RA procedure.

A two-step RA procedure may be initiated based on one or more case-basedprocedures, services, or radio conditions. One or more wireless devicesmay be configured (e.g., by a base station in the cell under itscoverage) to use a two-step RA procedure, for example, based on a cellidentified and/or indicated as small (e.g., there may be no need for aTA). A wireless device may acquire the configuration, via one or moreRRC messages (e.g., system information blocks, multicast and/or unicastRRC signaling), and/or via L1 control signaling (e.g., PDCCH order) usedto initiate a two-step RA procedure.

A wireless device (e.g., a stationary or near stationary wireless devicesuch as a sensor-type wireless device) may have a stored and/orpersisted TA value. A two-step RA procedure may be initiated based onthe stored and/or persisted TA value. A base station having macrocoverage may use broadcasting and/or dedicated signaling to configure atwo-step RA procedure with one or more wireless devices having storedand/or persisted TA values under the coverage.

A wireless device in an RRC connected state may perform a two-step RAprocedure. The two-step RA procedure may be initiated if a wirelessdevice performs a handover (e.g., network-initiated handover), and/or ifthe wireless device requires or requests a UL grant for a transmissionof delay-sensitive data and there are no physical-layer uplink controlchannel resources available to send (e.g., transmit) a schedulingrequest. A wireless device in an RRC INACTIVE state may perform atwo-step RA procedure for example, for a small data transmission whileremaining in the RRC INACTIVE state or for resuming a connection. Awireless device may initiate a two-step RA procedure, for example, forinitial access such as establishing a radio link, re-establishment of aradio link, handover, establishment of UL synchronization, and/or ascheduling request if there is no UL grant.

The following description presents one or more examples of a RACHprocedure. The procedures and/or parameters described in the followingmay not be limited to a specific RA procedure. The procedures and/orparameters described in the following may be applied for a four-step RAprocedure and/or a two-step RA procedure. A RA procedure may refer to afour-step RA procedure and/or a two-step RA procedure in the followingdescription.

A wireless device may receive (e.g., from a base station) one or moremessages indicating RA parameters of a four-step RA procedure (such asshown in FIG. 12) and/or a two-step RA procedure (such as shown in FIG.16). The one or more messages may be a broadcast RRC message, a wirelessdevice specific RRC message, and/or a combination thereof. The one ormore messages may comprise a RA configuration (e.g., at least one of:RACH-ConfigCommon, RACH-ConfigGeneric, and/or RACH-ConfigDedicated). Awireless device may receive, from a base station, a common and/or ageneric random access resource configuration (e.g., at leastRACH-ConfigCommon and/or RACH-ConfigGeneric), for example, based on acontention based (e.g., four-step and/or a two-step) RA procedure. Awireless device may receive, from a base station, a dedicated randomaccess resource configuration (e.g., at least RACH-ConfigDedicated), forexample, based on a contention free (four-step and/or a two-step) RAprocedure.

A base station may send (e.g., transmit), to a wireless device, one ormore messages indicating RA parameters. The one or more messages may bebroadcast via RRC message, via wireless device specific RRC message,and/or via a combination thereof. The one or more messages may compriseat least one of a common, generic, and/or dedicated random accessresource configuration (e.g., RACH-ConfigCommon, RACH-ConfigGeneric,and/or RACH-ConfigDedicated). A wireless device may receive, from a basestation, a common and/or a generic random access resource configuration(e.g., RACH-ConfigCommon and/or RACH-ConfigGeneric), for example, for acontention based RA procedure. A wireless device may receive, from abase station, at least a dedicated random access resource configuration(e.g., RACH-ConfigDedicated), for example, for a contention free RAprocedure.

FIG. 18 shows an example common random access resource configuration(e.g., a RACH-ConfigCommon IE). FIG. 19 shows example field descriptionsof a common random access resource configuration (e.g., aRACH-ConfigCommon IE). FIG. 20 shows an example generic random accessresource configuration (e.g., a RACH-ConfigGeneric IE), and examplefield descriptions. FIG. 21 shows an example dedicated random accessresource configuration (e.g., a RACH-ConfigDedicated IE). FIG. 22 showsexample field descriptions of the dedicated random access resourceconfiguration (e.g., RACH-ConfigDedicated).

A RA procedure may be initiated in different ways, for example, based atleast on one of a common random access resource configuration (e.g.,RACH-ConfigCommon), a generic random access resource configuration(e.g., RACH-ConfigGeneric), and/or a dedicated random access resourceconfiguration (e.g., RACH-ConfigDedicated). The RA procedure may beinitiated by a PDCCH order sent (e.g., transmitted) by a base station,by the wireless device (e.g., a MAC entity of a wireless device) of awireless device, and/or by RRC. A RA procedure may be ongoing at anypoint in time in a wireless device (e.g., a MAC entity of a wirelessdevice). A RA procedure on an SCell may be initiated by a PDCCH orderwith an index (e.g., ra-PreambleIndex) different from 0b000000. Thewireless device may continue with the ongoing procedure and/or startwith the new procedure (e.g. for an SI request), for example, if thewireless device (e.g., a MAC entity of a wireless device) receives arequest for a RA procedure at a time that another RA procedure isalready ongoing in the wireless device (e.g., a MAC entity of a wirelessdevice).

A base station may send (e.g., transmit) one or more RRC messages toconfigure a wireless device that include one or more parameters. Arandom access index parameter (e.g., prach-ConfigIndex) may indicate anavailable set of random access resource occasions (e.g., PRACHoccasions) for transmission of the RAP. A random access power parameter(e.g., preambleReceivedTargetPower) may indicate an initial RAP power.

A RSRP SSB threshold parameter (e.g., rsrp-ThresholdSSB) may indicate anRSRP threshold for a selection of the SSB and corresponding RAP and/orrandom access resource occasion (e.g., PRACH occasion). The RSRP SSBthreshold parameter may refer to a RSRP SSB threshold parameter in abeam failure recovery configuration (e.g., BeamFailureRecoveryConfigIE), for example, if the RA procedure is initiated for beam failurerecovery.

A RSRP CSI-RS threshold parameter (e.g., rsrp-ThresholdCSl-RS) mayindicate an RSRP threshold for the selection of CSI-RS and correspondingRAP and/or random access resource occasion (e.g., PRACH occasion). ARSRP CSI-RS threshold parameter may be set to a value calculated bymultiplying the RSRP CSI-RS threshold parameter in a beam failurerecovery configuration (e.g., BeamFailureRecoveryConfig IE) by a powercontrol offset parameter (e.g., powerControlOffset), for example, if theRA procedure is initiated for beam failure recovery. A RSRP SSB SULparameter (e.g., rsrp-ThresholdSSB-SUL) may indicate an RSRP thresholdfor the selection between the NUL carrier and the SUL carrier.

A power control offset parameter (e.g., powerControlOffset) may indicatea power offset between a RSRP SSB threshold parameter (e.g.,rsrp-ThresholdSSB) and a RSRP CSI-RS threshold parameter (e.g.,rsrp-ThresholdCSI-RS) to be used, for example, if the RA procedure isinitiated for beam failure recovery. A power ramping step parameter(e.g., powerRampingStep) may indicate a power-ramping factor. A powerramping step high priority parameter (e.g.,powerRampingStepHighPriority) may indicate a power-ramping factor incase of a differentiated RA procedure. A preamble index parameter (e.g.,ra-PreambleIndex) may indicate a RAP index.

FIG. 23 shows example random access occasion mask index values for arandom access occasion mask parameter (e.g., ra-ssb-OccasionMaskIndex).The random access occasion mask index values may define random accessresource occasion(s) (e.g., PRACH occasion) associated with an SSB inwhich the wireless device (e.g., a MAC entity of a wireless device) maysend (e.g., transmit) a RAP.

An occasion list parameter (e.g., ra-OccasionList) may define a randomaccess resource occasion(s) (e.g., PRACH occasion) associated with aCSI-RS in which the wireless device (e.g., a MAC entity of a wirelessdevice) may send (e.g., transmit) a RAP. A preamble maximum transmissionparameter (e.g., preambleTransMax) may define the maximum quantity ofRAP transmissions. A SSB mapping parameter (e.g.,ssb-perRACH-OccasionAndCB-PreamblesPerSSB) may define a quantity of SSBsmapped to each random access resource occasion (e.g., PRACH occasion). Aquantity of RAPs mapped to each SSBA RAP occasion parameter mayindicate: a set of RAPs and/or random access resource occasions (e.g.,PRACH occasions) for SI request, if any; and/or a set of RAPs and/orrandom access resource occasions (e.g., PRACH occasions) for beamfailure recovery request, if any. A response window parameter (e.g.,ra-ResponseWindow) may indicate a time window to monitor RAR(s). Acontention resolution timer parameter (e.g.,ra-ContentionResolutionTimer) may indicate a configuration for theContention Resolution Timer.

A RA procedure may be initiated for beam failure detection and recovery.A wireless device may be configured by RRC with a beam failure recoveryprocedure that may be used for indicating to the serving base station ofa SSB or CSI-RS, for example, if beam failure is detected on the servingSSB(s)/CSI-RS(s). Beam failure may be detected by counting beam failureinstance indication from the lower layers of the wireless device (e.g.,a MAC entity of a wireless device). A base station may configure, viaRRC, the parameters in a beam failure recovery configuration (e.g.,BeamFailureRecoveryConfig) for a beam failure detection and recoveryprocedure. A beam failure maximum count parameter (e.g.,beamFailurelnstanceMaxCount) may indicate a maximum count value for thebeam failure detection. A beam failure timer parameter (e.g.,beamFailureDetectionTimer) may indicate a configuration for a timer forthe beam failure detection. A beam failure recovery timer parameter(e.g., beamFailureRecoveryTimer) may indicate a configuration for atimer for a beam failure recovery procedure. A RSRP SSB threshold (e.g.,rsrp-ThresholdSSB) may indicate an RSRP threshold for the beam failurerecovery.

A power ramping step parameter (e.g., powerRampingStep) may indicate apower ramping factor for a beam failure recovery. A preamble targetpower parameter (e.g., preambleReceivedTargetPower) may indicate atarget power for the beam failure recovery. A maximum quantity ofpreambles parameter (e.g., preambleTransMax) may indicate a maximumquantity of preambles for the beam failure recovery. A response windowparameter (e.g., ra-ResponseWindow) may indicate a time window tomonitor response(s) for the beam failure recovery using contention-freeRAP. A random access configuration index parameter (e.g.,prach-ConfigIndex) may indicate a preamble format and PRACH subframeassignment index for the beam failure recovery. An occasion mask indexparameter (e.g., ra-ssb-OccasionMaskIndex) may indicate a SSB mask indexfor the beam failure recovery. An occasion list parameter (e.g.,ra-OccasionList) may indicate random access resource occasions for thebeam failure recovery.

A wireless device may use one or more parameters for a RA procedure. Awireless device may use at least one of PREAMBLE_INDEX;PREAMBLE_TRANSMISSION_ COUNTER; PREAMBLE_POWER_RAMPING_COUNTER;PREAMBLE_POWER RAMPING_STEP; PREAMBLE_RECEIVED_TARGET_POWER; PREAMBLE_BACKOFF; PCMAX; SCALING_FACTOR_BI; and/or TEMPORARY_C-RNTI.

A wireless device may perform random access resource selection forselecting one or more preambles and one or more random access resourceoccasions (e.g., PRACH occasions) (or resources comprising time,frequency, and/or code). A wireless device may determine one or moreoperations have occurred or settings configured. A RA procedure may beinitiated for beam failure recovery. The beamFailureRecoveryTimer may berunning or not configured. The contention-free random access resourcesfor beam failure recovery request associated with any of the SSBs and/orCSI-RSs may be explicitly provided by RRC signaling. At least one of theSSBs may be available, for example, based on SS-RSRP above a threshold(e.g., rsrp-ThresholdSSB) among the SSBs in a candidate beam list (e.g.,candidateBeamRSList), and/or the CSI-RSs with CSI-RSRP above a threshold(e.g., rsrp-ThresholdCSl-RS) among the CSI-RSs in a candidate beam list(e.g., candidateBeamRSList). The wireless device may select an SSB withSS-RSRP above a threshold (e.g., rsrp-ThresholdSSB) among the SSBs in acandidate beam list (e.g., candidateBeamRSList) or a CSI-RS withCSI-RSRP above a threshold (e.g., rsrp-ThresholdCSl-RS) among theCSI-RSs in a candidate beam list (e.g., candidateBeamRSList), forexample, based these observations by the wireless device. A wirelessdevice may set a PREAMBLE_INDEX to a preamble index parameter (e.g.,ra-PreambleIndex) corresponding to the SSB in a candidate beam list(e.g., candidateBeamRSList) which is quasi-collocated with the selectedCSI-RS, for example, if CSI-RS is selected, and there is nora-PreambleIndex associated with the selected CSI-RS. The wirelessdevice may set the PREAMBLE_INDEX to the preamble index parametercorresponding to the selected SSB or CSI-RS from the set of RAPs forbeam failure recovery request.

A RA procedure may be initiated and/or a preamble index parameter (e.g.,ra-PreambleIndex) may be explicitly provided via PDCCH and/or RRCsignaling. The preamble index parameter may not be 0b000000, and/or acontention-free random access resource associated with SSBs and/orCSI-RSs may not be explicitly provided by RRC signaling. A wirelessdevice may set the PREAMBLE_INDEX to the signaled preamble indexparameter.

A RA procedure may be initiated, and/or the contention-free randomaccess resources associated with SSBs may be explicitly provided, viaRRC, and at least one SSB with SS-RSRP above a threshold (e.g.,rsrp-ThresholdSSB) among the associated SSBs may be available. Thewireless device may select an SSB with SS-RSRP above the threshold(e.g., rsrp-ThresholdSSB) among the associated SSBs. The wireless devicemay set the PREAMBLE_INDEX to a preamble index parameter (e.g.,ra-PreambleIndex) corresponding to the selected SSB.

A wireless device may initiate a RA procedure. Contention-free randomaccess resources associated with CSI-RSs may be explicitly provided viaRRC signaling, and at least one CSI-RS with CSI-RSRP above a threshold(e.g., rsrp-ThresholdCSI-RS) among the associated CSI-RSs may beavailable. A wireless device may select a CSI-RS with CSI-RSRP above athreshold (e.g., rsrp-ThresholdCSl-RS) among the associated CSI-RSs. Thewireless device may set the PREAMBLE_INDEX to a preamble index parameter(e.g., ra-PreambleIndex) corresponding to the selected CSI-RS.

A wireless device may initiate a RA procedure, for example, based on atleast one of the SSBs with SS-RSRP above a threshold (e.g.,rsrp-ThresholdSSB) being available. A wireless device may select an SSBwith SS-RSRP above a threshold (e.g., rsrp-ThresholdSSB). Alternatively,the wireless device may select any SSB. The wireless device may performa random access resource selection, for example, if Msg3 is being resent(e.g., retransmitted). A wireless device may select a same group of RAPsas was used for the RAP transmission attempt corresponding to a firsttransmission of Msg3. A wireless device may select a preamble indexparameter (e.g., ra-PreambleIndex) randomly (e.g., with equalprobability from the RAPs associated with the selected SSB and theselected RAPs group), for example, if the association between RAPs andSSBs is configured. If the association between RAPs and SSBs is notconfigured, a wireless device may select a preamble index parameter(e.g., ra-PreambleIndex) randomly (e.g., with equal probability from theRAPs within the selected RAPs group). A wireless device may set thePREAMBLE_INDEX to the selected a preamble index parameter (e.g.,ra-PreambleIndex).

A wireless device may determine the next available random accessresource occasion (e.g., PRACH occasion) from the random access resourceoccasions (e.g., PRACH occasions) corresponding to the selected SSBpermitted by the restrictions given by the occasion mask index parameter(e.g., ra-ssb-OccasionMaskIndex), for example, if configured, if an SSBis selected, and/or an association between random access resourceoccasions (e.g., PRACH occasions) and SSBs is configured. The wirelessdevice (e.g., a MAC entity of a wireless device) may select a randomaccess resource occasion (e.g., PRACH occasion) randomly (e.g., withequal probability among the random access resource occasions (e.g.,PRACH occasions) occurring simultaneously but on different subcarriers,corresponding to the selected SSB). The wireless device (e.g., a MACentity of a wireless device) may take into account the possibleoccurrence of measurement gaps, for example, if determining the nextavailable random access resource occasion (e.g., PRACH occasion)corresponding to the selected SSB.

A wireless device may determine the next available random accessresource occasion (e.g., PRACH occasion) from the random access resourceoccasions (e.g., PRACH occasions) in an occasion list parameter (e.g.,ra-OccasionList) corresponding to the selected CSI-RS, for example, if aCSI-RS is selected and an association between random access resourceoccasions (e.g., PRACH occasions) and CSI-RSs is configured. Thewireless device (e.g., a MAC entity of a wireless device) may select arandom access resource occasion (e.g., PRACH occasion) randomly (e.g.,with equal probability among the random access resource occasions (e.g.,PRACH occasions) occurring simultaneously but on different subcarriers,corresponding to the selected CSI-RS). The wireless device (e.g., a MACentity of a wireless device) may take into account the possibleoccurrence of measurement gaps during determining the next availablerandom access resource occasion (e.g., PRACH occasion) corresponding tothe selected CSI-RS.

A wireless device may determine the next available random accessresource occasion (e.g., PRACH occasion) from the random access resourceoccasions (e.g., PRACH occasions), for example, permitted by therestrictions given by an occasion mask index parameter (e.g.,ra-ssb-OccasionMaskIndex), if configured. The occasion mask indexparameter may correspond to the SSB in the candidateBeamRSList, whichmay be quasi-collocated with the selected CSI-RS, if a CSI-RS isselected and/or if there is no contention-free random access resourceassociated with the selected CSI-RS. The wireless device (e.g., a MACentity of a wireless device) may take into account the possibleoccurrence of measurement gaps, for example, during determining the nextavailable random access resource occasion (e.g., PRACH occasion)corresponding to the SSB which may be quasi-collocated with the selectedCSI-RS.

A wireless device may determine a next available random access resourceoccasion (e.g., PRACH occasion). The wireless device (e.g., a MAC entityof a wireless device) may select a random access resource occasion(e.g., PRACH occasion) randomly (e.g., with equal probability among therandom access resource occasions (e.g., PRACH occasions) occurringsimultaneously but on different subcarriers). The wireless device (e.g.,a MAC entity of a wireless device) may take into account a possibleoccurrence of measurement gaps during determining the next availablerandom access resource occasion (e.g., PRACH occasion).

A wireless device may perform a RAP transmission, for example, based ona selected PREABLE INDEX and random access resource occasion (e.g.,PRACH occasion). A wireless device may increment a power ramping counter(e.g., PREAMBLE_POWER_RAMPING_COUNTER) by 1, for example, if anotification of suspending power ramping counter has not been receivedfrom lower layers (e.g., lower layer entities of the wireless device);and/or if SSB selected is not changed (e.g., a same SSB as a previousRAP transmission). The wireless device may select a value ofDELTA_PREAMBLE that may be predefined and/or semi-statisticallyconfigured by a base station. The wireless device may setPREAMBLE_RECEIVED_TARGET_POWER topreambleReceivedTargetPower+DELTA_PREAMBLE+(PREAMBLE_POWER_RAMPING_COUNTER−1)×PREAMBLE_POWER_RAMPING_STEP.The wireless device (e.g., via an entity of the wireless device) mayinstruct a physical layer entity of the wireless device to send (e.g.,transmit) the RAP via the selected random access resource (e.g., PRACH),corresponding RA-RNTI (if available), PREAMBLE_INDEX, and/orPREAMBLE_RECEIVED_TARGET_POWER. The wireless device may determine anRA-RNTI associated with the random access resource occasion (e.g., PRACHoccasion) in which the RAP is sent (e.g., transmitted). The RA-RNTIassociated with the PRACH in which the RAP is sent, may be determinedas:

RA-RNTI=1s_id+14×t_id+14×80×f_id+14×80×8×ul_carrier_id

s_id may be the index of the first OFDM symbol of the specified PRACH(0≤s_id≤14). t_id may be the index of the first slot of the specifiedPRACH in a system frame (0≤t_id≤80). fid may be the index of thespecified PRACH in the frequency domain (0≤f_id≤8). ul_carrier_id may bethe UL carrier used for Msg1 transmission (0 for NUL carrier, and 1 forSUL carrier).

An amount of data traffic carried over a network may be expected tochange over time. A quantity of users and/or devices may increase. Eachuser and/or device may access an increasing quantity and/or variety ofservices (e.g., video delivery, large files, images, etc.). Networkaccess may not only require high capacity, but also may causeprovisioning very high data rates to meet user expectations forinteractivity and/or responsiveness. More spectrum may be needed foroperators to meet the increasing demand It may be beneficial that morespectrum be made available for deploying macro cells as well as smallcells for communications systems, for example, considering userexpectations of high data rates along with seamless mobility.

There may be increasing interest from operators in deploying somecomplementary access utilizing unlicensed spectrum to meet trafficgrowth, for example, striving to meet the market demandsOperator-deployed Wi-Fi networks and the 3GPP standardization ofinterworking solutions with Wi-Fi (e.g., LTE/WLAN interworking) mayindicate operator interest. This interest may indicate that unlicensedspectrum, if present, may be an effective complement to licensedspectrum for network operators to help address traffic increase. In atleast some systems (e.g., LTE), licensed assisted access (LAA) and/ornew radio on unlicensed band(s) (NR-U) may offer an alternative foroperators to make use of unlicensed spectrum for managing a network.This use of unlicensed spectrum may offer new possibilities foroptimizing a network's efficiency.

LBT may be implemented for transmission in a cell (which may be referredto as an LAA cell and/or a NR-U cell). An LAA cell, NR-U cell, and/orany other cell may be interchangeable and may refer a cell operating inunlicensed band. The cell may be operated as non-standalone orstandalone, with or without an anchor cell in licensed band, configuredin an unlicensed band. An LBT procedure may comprise a clear channelassessment. In an LBT procedure, a wireless device and/or a base stationmay apply a clear channel assessment (CCA) check before using thechannel. The CCA may utilize at least energy detection to determine thepresence or absence of other signals on a channel in order to determinewhether a channel is occupied or clear. A regulation of a country mayalter configurations of the LBT procedure. European and Japaneseregulations may mandate the usage of LBT in the unlicensed bands, forexample, in a 5GHz unlicensed band. Carrier sensing via LBT may be usedfor equitable sharing of the unlicensed spectrum.

Discontinuous transmission on an unlicensed carrier with limited maximumtransmission duration may be enabled Channel reservation may be enabledby the transmission of signals (e.g., by an NR-U node), after gainingchannel access via a successful LBT operation. Channel reservation mayenable other nodes that receive a sent (e.g., transmitted) signal withenergy above a certain threshold a capability to sense the channel to beoccupied. Functions that may need to be supported by one or more signalsfor operation in unlicensed band with discontinuous downlinktransmission may include one or more of: detection of the downlinktransmission in unlicensed band (including cell identification) bywireless devices; and/or time and frequency synchronization of wirelessdevices.

DL transmission and frame structure design for an operation inunlicensed band may use subframe boundary alignment according to carrieraggregation timing relationships across serving cells aggregated by CA.Base station transmissions may not start at the subframe boundary. LAA,NR-U, and/or any other technologies may support sending messages viaPDSCH, for example, if not all OFDM symbols are available fortransmission in a subframe according to LBT. Delivery of necessarycontrol information for the PDSCH may also be supported.

LBT procedures may be used for coexistence of 3GPP systems (e.g., LTE,NR, and/or any other communications system or technology) with otheroperators and technologies operating in unlicensed spectrum. LBTprocedures on a node attempting to send (e.g., transmit) on a carrier inunlicensed spectrum may require the node to perform a clear channelassessment to determine if the channel is free for use. An LBT proceduremay involve, at least, energy detection to determine if the channel isbeing used. Regulatory requirements in some regions, (e.g., in Europe)may specify an energy detection threshold. If a node receives energygreater than a threshold, the node may determine that the channel is notclear. While nodes may follow such regulatory requirements, a node mayoptionally use a lower threshold for energy detection than thatspecified by regulatory requirements. NR-U and/or other technologies mayuse a mechanism to adaptively change the energy detection threshold. Amechanism may be used to adaptively lower the energy detection thresholdfrom an upper bound. An adaptation mechanism may not preclude static orsemi-static setting of the threshold. A Category 4 LBT mechanism orother type of LBT mechanisms may be implemented.

Various LBT mechanisms may be used. An LBT procedure may not beperformed by the transmitting entity, for example, for some signals. ACategory 1 (CAT1, e.g., no LBT) may be used. A channel in an unlicensedband may be held by a base station for DL transmission. A wirelessdevice may take over the channel for UL transmission. The wirelessdevice may perform the UL transmission without performing LBT. ACategory 2 (CAT2, e.g. LBT without random back-off) may be used. Theduration of time that the channel may be sensed to be idle before thetransmitting entity sends may be deterministic. A Category 3 (CAT3, e.g.LBT with random back-off with a contention window of fixed size) may beused. A transmitting entity may draw a random number N within acontention window. A size of the contention window may be specified by aminimum and maximum value of N. The size of the contention window may befixed. The random number N may be used in the LBT procedure to determinethe duration of time that the channel is sensed to be idle before thetransmitting entity sends via the channel

A Category 4 (CAT4, e.g. LBT with random back-off with a contentionwindow of variable size) may be used. A transmitting entity may draw arandom number N within a contention window. The size of contentionwindow may be specified by the minimum and maximum value of N. Thetransmitting entity may vary the size of the contention window based ondrawing the random number N. The random number N may be used in the LBTprocedure to determine the duration of time that the channel is sensedto be idle before the transmitting entity sends (e.g., transmits) on thechannel.

A wireless device may use uplink LBT. The UL LBT may be different fromthe DL LBT (e.g. by using different LBT mechanisms or parameters). TheUL may be based on scheduled access that affects a wireless device'schannel contention opportunities. Other UL LBT configurations include,but are not limited to, multiplexing of multiple wireless devices in asubframe (slot, and/or mini-slot).

A DL transmission burst may be a continuous transmission from a DLtransmitting node with no transmission immediately before or after fromthe same node via the same component carrier (CC). An UL transmissionburst from a wireless device perspective may be a continuoustransmission from a wireless device with no transmission immediatelybefore or after from the same wireless device via the same CC. An ULtransmission burst may be defined from a wireless device perspective. AnUL transmission burst may be defined from a base station perspective. Abase station may operate DL+UL via a same unlicensed carrier. DLtransmission burst(s) and UL transmission burst(s) may be scheduled in aTDM manner via the same unlicensed carrier. An instant in time may bepart of a DL transmission burst or an UL transmission burst.

Channel observation time (COT) sharing may be used. COT sharing may be amechanism (e.g., enabled by ETSI-BRAN) wherein one device acquires a COTusing CAT4 LBT and another device shares it using a 25 μs LBT with agap, for example, provided the amount of transmission does not exceedthe MCOT limit for the given priority class. COT sharing may allow aconcession for UL via an unlicensed band in which a base station sends(e.g., transmits) a grant to a wireless device before it can be sent(e.g., transmitted) via the UL. The delay between the grant and thecorresponding UL transmission may be a period of time (e.g., at least 4ms). A pause (e.g., 4 ms) may not be accounted in the COT duration. Abase station may indicate the remaining time to one or more wirelessdevices via a PDCCH, for example, if the base station acquired a COT andsent a message indicating the COT via the DL without exhausting the fullCOT. The wireless device may perform UL transmissions with dynamic grantand/or configured grant (e.g., Type 1, Type2, autonomous UL) with 25 μsLBT in the configured period

Single and multiple DL to UL and UL to DL switching within a shared COTmay be supported. LBT requirements to support single or multipleswitching points, may be different for different gaps. No-LBT may beused, for example, for a gap of less than 16 μs. A one-shot LBT may beused, for example, for a gap of between 16 μs and 25 μs. A one-shot LBTmay be used, for example, for single switching point, and for the gapfrom DL transmission to UL transmission exceeding 25 μs. A one-shot LBTmay be used, for example, for multiple switching points, and for the gapfrom DL transmission to UL transmission exceeding 25 μs.

A signal that facilitates detection with low complexity may be usefulfor wireless device power saving, improved coexistence, spatial reuse(which may be within the same operator network), serving celltransmission burst acquisition, etc. Operation of at least sometechnologies (e.g., NR-U) may use a signal comprising at least SS/PBCHblock burst set transmission. Other channels and signals may be senttogether as part of the signal. The design of this signal may determinethat there are no gaps within the time span the signal is sent, forexample, at least within a beam. Gaps may be needed for beam switching.The occupied channel bandwidth may be satisfied. A block-interlacedbased message via a PUSCH may be used. The same interlace structure formessages via a PUCCH and/or a PUSCH may be used. Interlaced basedmessages via a PRACH may be used.

An initial active DL/UL BWP may be approximately 20 MHz for a firstunlicensed band (e.g., 5 GHz band). An initial active DL/UL BWP may beapproximately 20 MHz for a second unlicensed band (e.g., 6 GHz band), ifsimilar channelization as the first unlicensed band (e.g., 5 GHz band)is used for the second unlicensed band (e.g., 6 GHz band). Wideband maybe configured (e.g., by a base station) with one or more BWPs. Four BWPsmay be configured (e.g., by a base station), for example, with about 20MHz bandwidth configured for each BWP, or 80 MHz allocated for the fourBWPs. An active BWP (DL and/or UL) may be switched one to another atleast based on BWP switching mechanism. The wideband may be configured(e.g., by a base station) with one or more subbands. Four subbands maybe configured (e.g., by a base station), for example, with about 20 MHzconfigured for each subband, or 80 MHz allocated for the four subbands.A wireless device may perform an LBT procedure subband by subband, andmay send (e.g., transmit) data via scheduled resources on one or moresubbands where the LBT procedure indicates idle.

HARQ acknowledge and negative acknowledge (A/N) for the correspondingdata may be sent in the same shared COT. The HARQ A/N may be sent in aseparate COT from the one the corresponding data was sent. Flexibletriggering and/or multiplexing of HARQ feedback may be used for one ormore DL HARQ processes, for example, if UL HARQ feedback is sent onunlicensed band. The dependencies of HARQ process information to thetiming may be removed. UCI messages via PUSCH may carry HARQ process ID,NDI, RVID. Downlink Feedback Information (DFI) may be used fortransmission of HARQ feedback for a configured grant.

CBRA and CFRA may be supported on an SpCell. CFRA may be supported onSCells. An RAR may be sent via an SpCell, for example, in anon-standalone configuration. An RAR may be sent via an SpCell and/orvia an SCell, for example, in a standalone configuration. A predefinedHARQ process ID for an RAR may be used.

Carrier aggregation between a licensed band PCell (e.g., NR (PCell)) andan SCell (e.g., NR-U (SCell)) may be supported. An SCell may have bothDL and UL, or DL-only. Dual connectivity between various licensed bandPCells (e.g., LTE (PCell)) and PSCells (e.g., NR-U (PSCell)) may besupported. Stand-alone cells (e.g., NR-U) in which all carriers are inone or more unlicensed bands may be supported. A cell (e.g., an NR cell)with a DL in an unlicensed band and an UL in a licensed band, or viceversa, may be supported. Dual connectivity between licensed band cells(e.g., a NR (PCell) and NR-U (PSCell)) may be supported.

An operating bandwidth may be an integer multiple of 20 MHz, forexample, if an absence of Wi-Fi cannot be guaranteed (e.g., byregulation) in a band (e.g., sub-7 GHz) via which a communicationsnetwork or system (e.g., NR-U) is operating. LBT may be performed inunits of 20 MHz, for example, for bands where absence of Wi-Fi cannot beguaranteed (e.g., by regulation). Receiver assisted LBT (e.g., RTS/CTStype mechanism) and/or on-demand receiver assisted LBT (e.g., forexample receiver assisted LBT enabled only if needed) may be used.Techniques to enhance spatial reuse may be used. Preamble detection maybe used.

A network may gain access to the channel to send (e.g., transmit) amessage via PDCCH such that a wireless device may need to perform LBTagain prior to sending via the channel, for example, with scheduledPUSCH transmissions via an unlicensed carrier. The procedure may tend toincrease latency and may become worse if the channel is loaded. Amechanism of autonomous uplink transmission may be used. A wirelessdevice may be pre-allocated with a resource for transmission (e.g.,similar to UL SPS) and may perform LBT prior to using the resource.Autonomous uplink may be based on the configured grant functionality(e.g., Type 1 and/or Type 2).

A HARQ process identity may be sent by the wireless device (e.g., asUCI). A wireless device may use the first available transmissionopportunity irrespective of the HARQ process. UCI messages via PUSCH maybe used to carry HARQ process ID, NDI and RVID.

A UL dynamic grant scheduled UL transmission may increase a delay and/ortransmission failure possibility due to at least two LBTs of thewireless device and the base station, for example, for unlicensed bands.A pre-configured grant (e.g., such as configured grant in NR) may beused (e.g., such as for NR-U). The pre-configured grant may decrease aquantity of LBTs performed and control signaling overhead. An uplinkgrant may be provided by an RRC message (e.g., in a Type 1 configuredgrant). An uplink grant may be stored as configured uplink grant. Anuplink grant (e.g., a Type 1 configured grant) may be initiated based onor in response to receiving the RRC. An uplink grant may be provided bya PDCCH. An uplink grant may be stored and/or cleared as a configureduplink grant, for example, based on L1 signaling indicating configuredgrant activation and/or deactivation (e.g. using a Type 2 configuredgrant).

A dependency between HARQ process information to the timing may notexist. UCI messages via a PUSCH may carry HARQ process ID, NDI, RVID,etc. A wireless device may autonomously select one HARQ process ID thatis informed to a base station by UCI message(s). A wireless device mayperform non-adaptive retransmission with the configured uplink grant.The wireless device may attempt to send (e.g., transmit) in the nextavailable resource with configured grant, for example, if dynamic grantfor configured grant retransmission is blocked due to LBT.

Downlink Feedback Information (DFI) may be sent (e.g., using DCI) andmay include HARQ feedback for configured grant transmission. Thewireless device may perform transmission/retransmission using configuredgrant according to DFI comprising HARQ feedback. Wideband carrier withmore than one channels may be supported, for example, via an unlicensedcell.

There may be one active BWP in a carrier. A BWP with one or morechannels may be activated. LBT may be performed in units of 20 MHz, forexample, if absence of Wi-Fi cannot be guaranteed (e.g., by regulation).There may be multiple parallel LBT procedures for a BWP. The actualtransmission bandwidth may be subject to subband with LBT success, whichmay result in dynamic bandwidth transmission within the active widebandBWP.

One or more active BWPs may be supported. The BWP bandwidth may be thesame as the bandwidth of subband for LBT (e.g., LBT may be carried outon each BWP), for example, which may improve the BWP utilizationefficiency. The network may activate and/or deactivate the BWPs based ondata volume to be sent.

One or more non-overlapped BWPs may be activated for a wireless devicewithin a wide component carrier (e.g., which may be similar to carrieraggregation in LTE LAA). The BWP bandwidth may be the same as thebandwidth of subband for LBT (e.g., LBT may be carried out on each BWP),for example, which may improve the BWP utilization efficiency. Awireless device may have a capability to support one or more narrow RFand/or a wide RF which may comprise the one or more activated BWPs, forexample, if more than one subband LBT success occurs.

A single wideband BWP may be activated for a wireless device within acomponent carrier. The bandwidth of wideband BWP may be in the unit ofsubband for LBT. The wideband BWP bandwidth may comprise multiple 20MHz, for example, if the subband for LBT is 20 MHz in 5 GHz band. Anactual transmission bandwidth may be subject to subband with LBTsuccess, which may result in dynamic bandwidth transmission within thisactive wideband BWP.

Active BWP switching may be achieved using scheduling DCI. The networkmay indicate to a wireless device a new active BWP to use for anupcoming, and/or any subsequent, data transmission/reception. A wirelessdevice may monitor multiple, configured BWPs to determine which has beenacquired for DL transmissions by the base station. A wireless device maybe configured with a monitoring occasion periodicity and/or offset foreach configured BWP. The wireless device may determine if a BWP has beenacquired by the base station during the monitoring occasions. Thewireless device may continue with a BWP as its active BWP, for example,at least until indicated otherwise or a Maximum Channel Occupancy Time(MCOT) has been reached, and/or after successfully determining that thechannel is acquired. A wireless device may attempt blind detection ofPDCCH information in configured CORESETs, for example, if a wirelessdevice has determined that a BWP is active. The wireless device mayperform measurements on aperiodic and/or SPS resources.

A wireless device may be configured with multiple UL resources, whichmay be in different BWPs, for example, for UL transmissions. Thewireless device may have multiple LBT configurations, each associatedwith a BWP and/or a beam pair link. The wireless device may be grantedwith UL resources associated with (e.g., linked to) one or more LBTconfigurations. The wireless device may be provided with (e.g., madeavailable, received, stored, etc.) multiple autonomous uplink (AUL)and/or grant-free resources, each using different LBT configurations.Providing a wireless device with multiple AUL resources over multipleBWPs may ensure that if LBT fails using a first LBT configuration for afirst AUL resource in one BWP, a wireless device may attempttransmission in a second AUL resource in another BWP. This use ofmultiple AUL resources may reduce the channel access latency and/orimprove spectral efficiency of the over-all unlicensed carrier.

Carrier aggregation with at least one SCell operating in an unlicensedspectrum may be performed in LAA. A configured set of serving cells fora wireless device may include at least one SCell operating in anunlicensed spectrum according to a first frame structure (e.g., framestructure Type 3). An SCell operating in LAA may be referred to as anLAA SCell.

A maximum frequency separation between any two carrier centerfrequencies on which LAA SCell transmissions are performed may be lessthan or equal to 62 MHz (or any other frequency), for example, if theabsence of devices (e.g., IEEE802.11n/11ac devices) sharing the carriercannot be guaranteed on a long term basis (e.g., by regulation), and/orif the maximum quantity of unlicensed channels via which a network maysimultaneously send is equal to or less than 4 (or any other quantity).A wireless device may be required to support frequency separation.

A base station and/or a wireless device may apply LBT before performinga transmission on an LAA SCell. A transmitter (e.g., of a wirelessdevice and/or of a base station) may listen to and/or sense the channelto determine whether the channel is free or busy, for example, if LBT isapplied. The transmitter may perform the transmission, if the channel isdetermined to be free and/or clear. The transmitter may not perform thetransmission, if the channel is not determined to be free and/or clear.A base station may continue to meet a LAA maximum energy detectionthreshold requirement, for example, if the base station uses channelaccess signals (e.g., of other technologies) for the purpose of channelaccess.

A combined time of transmissions compliant with the channel accessprocedure by a base station may not exceed a threshold time period(e.g., 50 ms) in any contiguous time period (e.g., 1 second period) onan LAA SCell. An LBT type (e.g., type 1 or type 2 uplink channel access)that the wireless device applies may be signaled via uplink grant foruplink PUSCH message transmission on LAA SCells. For AUL messagetransmissions the LBT may not be signaled via the uplink grant.

FIG. 24 shows an example channel access priority class values. A basestation may signal the channel access priority class for a logicalchannel, for example, for type 1 uplink channel access on AUL. Awireless device may select a highest channel access priority class(e.g., with a lower number) of the logical channel(s) with a MAC SDUmultiplexed into a MAC PDU. The MAC CEs (e.g., except padding BSR) mayuse the lowest channel access priority class. The wireless device mayselect logical channels corresponding to any channel access priorityclass for UL transmission in the subframes signaled by a base stationvia common downlink control signaling, for example, for type 2 uplinkchannel access on AUL.

A base station may not schedule a wireless device with more subframesthan a minimum necessary to send (e.g., transmit) traffic correspondingto a selected channel access priority class or lower (e.g., having alower number) than the channel access priority class signaled in a ULgrant. The base station may schedule the wireless device, for example,based on: the latest BSR and/or received uplink traffic from thewireless device (e.g., for uplink LAA operation), if type 1 uplinkchannel access procedure is signaled to the wireless device; channelaccess priority class used by the base station based on the downlinktraffic; and/or the latest BSR and/or received UL traffic from thewireless device, if type 2 uplink channel access procedure is signaledto the wireless device.

A first quantity (e.g., four) of channel access priority classes may beused during performing uplink and downlink transmissions in LAAcarriers. A channel access priority class may be used by trafficbelonging to different standardized QCIs. A non-standardized QCI (e.g.,operator specific QCI) may use a suitable channel access priority classof the standardized QCIs that best matches the traffic class of thenon-standardized QCI. For uplink, the base station may select a channelaccess priority class by taking into account the lowest priority QCI ina logical channel group.

Four (or any other quantity) channel access priority classes may beused. A base station may ensure several requirements and/or limitations,for example, if a DL transmission burst with PDSCH is sent, for whichchannel access has been obtained using channel access priority class P(1 . . . 4). The base station may limit the transmission duration of theDL transmission burst so as to not exceed a minimum duration needed tosend (e.g., transmit) all available buffered traffic corresponding tochannel access priority class(es)≤P. The base station may limit thetransmission duration of the DL transmission burst so as to not exceed amaximum channel occupancy time for channel access priority class P. Thebase station may ensure additional traffic corresponding to channelaccess priority class(s)>P be included in the DL transmission burst onceno more data corresponding to channel access priority class≤P isavailable for transmission. The base station may maximize occupancy ofthe remaining transmission resources in the DL transmission burst withsuch additional traffic. A DL transmission burst may refer to acontinuous transmission by the base station after a successful LBT.

A wireless device may be scheduled for downlink transmission via a PDCCHof a serving cell. A wireless device may be scheduled for uplinktransmission via a PDCCH of one other serving cell, for example, if thePDCCH of an LAA SCell is configured and/or if cross-carrier schedulingapplies to uplink transmission. The wireless device may be scheduled foruplink transmission and downlink transmission via its PDCCH, forexample, if the PDCCH of an LAA SCell is configured and/or ifself-scheduling applies to both uplink transmission and downlinktransmission.

FIG. 25 shows an example BWP configuration information element (e.g., aBWP IE). A BWP IE may be used to configure a BWP. The network mayconfigure at least an initial BWP comprising at least a downlink BWP andone (e.g., if the serving cell is configured with an uplink) or two(e.g., if using supplementary uplink (SUL)) uplink BWPs, for example,for each serving cell. The network may configure additional uplink anddownlink BWPs for a serving cell.

The BWP configuration may be split into uplink and downlink parametersand/or into common and dedicated parameters. Common parameters (e.g.,BWP-UplinkCommon and BWP-DownlinkCommon) may be cell specific and/or thenetwork may ensure the necessary alignment with corresponding parametersof other wireless devices. Common parameters of the initial BWP of thePCell may be provided via system information. The network may providethe common parameters via dedicated signaling.

A field, IE, or prefix (e.g., cyclic prefix) may indicate whether to usethe extended cyclic prefix for this BWP. The wireless device may use thenormal cyclic prefix (CP), for example, if the CP is not set. Normal CPmay be supported for all numerologies and slot formats. Extended CP maybe supported only for 60 kHz subcarrier spacing (or some other frequencysubcarrier spacing). A parameter (e.g., locationAndBanddwidth) mayindicate a frequency domain location and/or a bandwidth of this BWP. Thevalue of the field may be interpreted as a RIV. A first PRB may be a PRBdetermined by a subcarrier spacing parameter (e.g., subcarrierSpacing)of this BWP and/or an offset parameter (e.g., offsetToCarrier(configured in SCS-SpecificCarrier contained within FrequencylnfoDL))corresponding to this subcarrier spacing. A BWP-pair (e.g., UL BWP andDL BWP with the same index) may have the same center frequency, forexample, based on use of TDD. The subcarrier spacing parameter mayindicate subcarrier spacing to be used in this BWP for channels andreference signals unless explicitly configured elsewhere. The valuekHz15 may correspond to μ=0, kHz30 to μ=1, and so on. The values 15, 30,or 60 kHz may be used. A BWP index (e.g., bwp-Id) may indicate anidentifier for a BWP.

Other parts of the RRC configuration may use the BWP index (e.g.,BWP-Id) to associate with a particular BWP. A BWP ID=0 may be associatedwith an initial BWP and/or may not be used with other BWPs. The network(NW) may trigger the wireless device to switch UL or DL BWP using a DCIfield. The four code points in the DCI field may map to theRRC-configured BWP index (e.g., BWP-Id). The DCI code point may beequivalent to the BWP ID (initial=0, first dedicated=1, . . .), forexample, for up to three configured BWPs (in addition to the initialBWP). The BWPs may be identified by DCI code points 0 to 3, for example,if the NW configures 4 dedicated BWPs. It may not be possible to switchto the initial BWP using the DCI field, for example, with thisconfiguration. The BWP index (e.g., bwp-Id) may indicate an identifierfor a BWP. Other parts of the RRC configuration may use the BWP index(e.g., BWP-Id) to associate themselves with a particular BWP. A BWP ID=0may be associated with the initial BWP and may not be used in otherBWPs.

The NW may trigger the wireless device to switch an UL BWP and/or a DLBWP using a DCI field. The four code points in that DCI field may map tothe RRC-configured BWP index (e.g., BWP-ID). The DCI code point may beequivalent to the BWP index (e.g., BWP ID where initial=0, firstdedicated=1, . . .), for example, for up to three configured BWPs (inaddition to the initial BWP). The BWPs may be identified by DCI codepoints 0 to 3, for example, if the NW configures four dedicated BWPs. Itmay not be possible to switch to the initial BWP using the DCI field,for example, with this configuration. A common random accessconfiguration (e.g., rach-ConfigCommon) may indicate configuration ofcell specific RA parameters that the wireless device may use forcontention based random access, contention free random access, and/orcontention based beam failure recovery. The NW may configure SSB-basedRA (including RACH-ConfigCommon) for UL BWPs, for example, based on thelinked DL BWPs allowing the wireless device to acquire the SSBassociated to the serving cell. An uplink control channel configuration(e.g., PUCCH-config) may indicate an uplink control channelconfiguration (e.g., PUCCH configuration) for one BWP of the regular ULor SUL of a serving cell. The network may configure PUCCH on the BWPs ofone of the uplinks (UL or SUL), for example, if the wireless device isconfigured with SUL.

The network may configure PUCCH-Config for each SpCell. The network mayconfigure one additional SCell of a cell group with an uplink controlchannel configuration (e.g., PUCCH-Config for a PUCCH SCell), forexample, if supported by the wireless device. The IE BWP-Id may be usedto refer to BWP. The initial BWP may be referred to by a zero index(e.g., BWP-Id 0). The other BWPs may be referred to by a non-zero index(e.g., BWP-Id 1 to a maximum number/quantity of BWPs (e.g.,maxNrofBWPs)).

FIG. 26 shows an example serving cell configuration information element.A serving cell configuration (e.g., ServingCellConfig IE) may be used toconfigure (e.g., add or modify) the wireless device with a serving cell.The serving cell may be the SpCell or an SCell of an MCG or SCG. Theparameters of the serving cell configuration may comprise wirelessdevice specific parameters and/or cell specific parameters (e.g.additionally configured BWPs).

An inactivity timer (e.g., bwp_InactivityTimer) may be configured tohave a duration in milliseconds (ms) after which the wireless device mayfall back to the default BWP. A value 0.5 ms may be applicable forcarriers greater than 6 GHz. If the network releases the timerconfiguration, the wireless device may stop the timer without switchingto the default BWP.

A default downlink BWP index (e.g., defaultDownlinkBWP-Id) maycorrespond to a default L1 downlink BWP parameter (e.g.,‘default-DL-BWP’). The initial BWP may be referred to by a BWP index(e.g., BWP-Id=0). The ID of the downlink BWP may be used after timerexpiry. This ID field may be wireless device specific. The wirelessdevice may use the initial BWP as default BWP, for example, if the fieldis absent.

A downlink BWP list (e.g., downlinkBWP-ToAddModList) may indicate a listof additional downlink BWPs to be added or modified. A downlink BWPrelease list (e.g., downlinkBWP-ToReleaseList) may indicate a list ofadditional downlink BWPs to be released.

The active DL BWP index may contain the ID of the DL BWP to beactivated, for example, based on or upon performing the reconfigurationin which it is received, for example, if an active DL BWP index (e.g.,firstActiveDownlinkBWP-Id) is configured for an SpCell. The RRCreconfiguration may not impose a BWP switch (which may correspond to L1parameter ‘active-BWP-DL-Pcell’), for example, if the field is absent.The field may contain the ID of the downlink BWP to be used uponMAC-activation of an SCell, for example, if configured for an SCell. Theinitial BWP may be referred to by a zero index (e.g., BWP-Id=0).

An initial DL BWP parameter (e.g., initialDownlinkBWP) may indicate adedicated (e.g., UE-specific) configuration for the initial downlinkbandwidth-part. An active UL BWP index (e.g., firstActiveUplinkBWP-Id)may contain an ID of the DL BWP to be activated upon performing thereconfiguration in which it is received, for example, if configured foran SpCell. The RRC reconfiguration may not impose a BWP switch (e.g.,corresponding to L1 parameter ‘active-BWP-UL-Pcell’), for example, ifthe field is absent. The field may contain the ID of the uplink BWP tobe used upon MAC-activation of an SCell, for example, if configured foran SCell. The initial BWP may be used in a BWP parameter (e.g.,BandwidthPartId=0). An initial uplink BWP parameter (e.g.,initialUplinkBWP) may indicate a dedicated (UE-specific) configurationfor the initial uplink bandwidth-part.

FIG. 27A, FIG. 27B, and FIG. 27C show respectively examples of RAR, MACsubheader with backoff indicator (BI), and a MAC subheader with a RAPID.A wireless device may receive from a base station at least one RAR as aresponse of Msg1 1220 (as shown in FIG. 12) or two-step Msg1 1620 (shownin FIG. 16) using an RA procedure. An RAR may be in a form of MAC PDUcomprising one or more MAC subPDUs and/or (optionally) padding. FIG. 27Ais an example of an RAR. A MAC subheader may be octet-aligned. Each MACsubPDU may comprise one or more of the following: a MAC subheader withBI only; a MAC subheader with RAPID only (e.g., acknowledgment for SIrequest); a MAC subheader with RAPID and MAC RAR. FIG. 27B shows anexample of a MAC subheader with BI. A MAC subheader with BI may compriseone or more header fields (e.g., E/T/R/R/BI) as shown in FIG. 27B anddescribed below. A MAC subPDU with BI may be placed at the beginning ofthe MAC PDU, if included. MAC subPDU(s) with RAPID only, and/or MACsubPDU(s) with RAPID and MAC RAR, may be placed anywhere after a MACsubPDU with BI and, before padding as shown in FIG. 27A. A MAC subheaderwith RAPID may comprise one or more header fields (e.g., E/T/RAPID) asshown in FIG. 27C. Padding may be placed at the end of the MAC PDU, ifpresent. Presence and length of padding may be implicit, for example,based on TB size, and/or a size of MAC subPDU(s).

A field (e.g., an E field) in a MAC subheader may indicate an extensionfield that may be a flag indicating if the MAC subPDU (including the MACsubheader) is the last MAC subPDU or not in the MAC PDU. The E field maybe set to “1” to indicate at least one more MAC subPDU follows. The Efield may be set to “0” to indicate that the MAC subPDU including thisMAC subheader is a last MAC subPDU in the MAC PDU. A field (e.g., a Tfield) may be a flag indicating whether the MAC subheader contains aRAPID or a BI (e.g., one or more backoff values may predefined and BImay indicate one of backoff value). The T field may be set to “0” toindicate the presence of a a field (e.g., a BI field) in the subheader.The T field may be set to “1” to indicate the presence of a RAPID fieldin the subheader. A field (e.g., an R field) may indicate a reserved bitthat may be set to “0.” A field (e.g., a BI field) may indicate anoverload condition in the cell. A size of the BI field may be 4 bits. Afield (e.g., a RAPID field) may be a RAPID field that may identifyand/or indicate the transmitted RAP. A MAC RAR may not be included inthe MAC subPDU, for example, based on the RAPID in the MAC subheader ofa MAC subPDU corresponding to one of the RAPs configured for an SIrequest.

There may be one or more MAC RAR formats. At least one MAC RAR formatmay be employed in a four-step or a two-step RA procedure.

FIG. 28 shows an example MAC RAR format. The MAC RAR may be fixed sizeas shown in

FIG. 28. The MAC RAR may comprise one or more of the following fields:an R field that may indicate a reserved bit, which may be set to “0”; atiming advance (TA) command field that may indicate the index value forTA employed to control the amount of timing adjustment; a UL grant fieldthat indicates the resources to be employed on an uplink; and an RNTIfield (e.g., temporary C-RNTI and/or C-RNTI) that may indicate anidentity that is employed during RA. An RAR may comprise one or more offollowing for a two-step RA procedure: a UE contention resolutionidentity, an RV ID for retransmission of one or more TBs, decodingsuccess or failure indicator of one or more TB transmissions, and one ormore fields from the MAC RAR formats.

A base station may multiplex, in a MAC PDU, RARs for two-step and/orfour-step RA procedures. A wireless device may not use an RAR lengthindicator field. The wireless device may determine the boundary of eachRAR in the MAC PDU based on pre-determined RAR size information, forexample, based on RARs for two-step and four-step RA procedures havingthe same size.

FIG. 29 shows an example RAR format. The RAR format may be employed in aMAC PDU, for example, that may multiplex RARs for two-step and four-stepRA procedures. The RAR shown in FIG. 29 may use a fixed size, forexample, using the same format for two-step and four-step RA procedures.

FIG. 30A, and FIG. 30B show example RAR formats. The RAR formats may beemployed for a two-step RA procedure. An RAR for a two-step RA proceduremay have a different format, size, and/or fields, from an RAR for afour-step RA procedure. An RAR may have a field to indicate a type ofRAR (e.g., a reserved “R” field as shown in FIG. 28, for example, basedon RARs for two-step and four-step RA procedures being multiplexed intoa MAC PDU, and/or the RARs having different formats between two-step andfour-step RA procedure). FIG. 30A, and FIG. 30B may be employed toindicate a type of RAR. A field for indicating an RAR type may be in asubheader (such as a MAC subheader) and/or in an RAR. An RAR maycomprise different types of fields that may correspond with an indicatorin a subheader and/or in an RAR. A wireless device may determine theboundary of one or more RARs in a MAC PDU, for example, based on one ormore indicators.

A serving cell may be configured with one or multiple BWPs. a maximumnumber of BWP per serving cell may be a first number. BWP switching fora serving cell may be used to activate an inactive BWP and deactivate anactive BWP at a determined time. BWP switching may be controlled by aPDCCH message (e.g., signal) indicating a downlink assignment or anuplink grant (e.g., by the bwp-InactivityTimer, by RRC signalling, or bythe wireless device (e.g., MAC entity of the wireless device) itselfupon initiation of RA procedure). The DL BWP and UL BWP indicated by afirst active downlink BWP identifier (e.g., firstActiveDownlinkBWP-Id)and a first active uplink BWP identifier (e.g., firstActiveUplinkBWP-Id)respectively may be active without receiving a message (e.g., signal)via PDCCH indicating a downlink assignment or an uplink grant, forexample, based on or in response to addition of an SpCell or activationof an SCell. The active BWP for a serving cell may be indicated byeither an RRC message or PDCCH message (e.g., signal). A DL BWP may bepaired with a UL BWP, and BWP switching may be common for both UL andDL, for example, based on an unpaired spectrum.

An activated serving cell may be configured with a BWP. A BWP may beactivated and the wireless device (e.g., MAC entity of the wirelessdevice) may: send (e.g., transmit) via a UL-SCH on the BWP; send (e.g.,transmit) via a RACH on the BWP; monitor or continue to monitor thePDCCH on the BWP; send (e.g., transmit) a PUCCH signal on the BWP; send(e.g., transmit) an SRS signal on the BWP; receive a DL-SCH message onthe BWP; and/or (re-)initialize any suspended configured uplink grantsof configured grant Type 1 on the active BWP. The BWP activation may bebased on a stored configuration, if any.

An activated serving cell may be configured with a BWP. The BWP may bedeactivated and the wireless device (e.g., MAC entity of the wirelessdevice) may: not send (e.g., transmit) via a UL-SCH on the BWP; not send(e.g., transmit) via a RACH on the BWP; may not monitor or continue tonot monitor the PDCCH on the BWP; not send (e.g., transmit) via a PUCCHon the BWP; not report CSI for the BWP; not send (e.g., transmit) an SRSsignal on the BWP; not receive a DL-SCH message on the BWP; clear anyconfigured downlink assignment and configured uplink grant of configuredgrant Type 2 on the BWP; and suspend any configured uplink grant ofconfigured grant Type 1 on the inactive BWP.

The wireless device (e.g., MAC entity of the wireless device) may switchthe active UL BWP to BWP indicated by an initial uplink BWP parameter(e.g., initialUplinkBWP), for example, based on or in response toinitiation of the RA procedure on a serving cell and/or, PRACH occasionsnot being configured for the active UL BWP. The wireless device (e.g.,MAC entity of the wireless device) may switch the active DL BWP to BWPindicated by an initial downlink BWP parameter (e.g.,initialDownlinkBWP), for example, based on the serving cell being aSpCell. The wireless device (e.g., MAC entity of the wireless device)may perform the RA procedure on the active DL BWP of SpCell and activeUL BWP of this serving cell.

The wireless device (e.g., MAC entity of the wireless device) may switchthe active DL BWP to the DL BWP with the same BWP index (e.g., bwp-Id)as the active UL BWP, for example, based on or in response to initiationof the RA procedure on a serving cell, the PRACH occasions beingconfigured for the active UL BWP, the serving cell is a SpCell, and/orif the active DL BWP does not have the same BWP index (e.g., bwp-Id) asthe active UL BWP. The wireless device (e.g., MAC entity of the wirelessdevice) may perform the RA procedure on the active DL BWP of SpCell andactive UL BWP of this serving cell.

The wireless device (e.g., MAC entity of the wireless device) mayperform BWP switching to a BWP indicated by a PDCCH message, forexample, based on the wireless device (e.g., MAC entity of the wirelessdevice) receiving a PDCCH message for BWP switching of a serving cell;there being no ongoing RA procedure associated with this serving cell;and/or the ongoing RA procedure associated with this serving cell beingsuccessfully completed upon reception of the PDCCH message addressed toC-RNTI. A wireless device may determine whether to switch BWP or ignorethe PDCCH message for BWP switching, for example, based on the wirelessdevice (e.g., MAC entity of the wireless device) receiving a PDCCHmessage for BWP switching for a serving cell while a RA procedureassociated with that serving cell is ongoing in the wireless device(e.g., MAC entity of the wireless device).The wireless device mayperform BWP switching to a BWP indicated by the PDCCH message, forexample, based on the PDCCH reception for BWP switching addressed to theC-RNTI for successful RA procedure completion. The wireless device(e.g., MAC entity of the wireless device) may stop the ongoing RAprocedure and may initiate a RA procedure on the new activated BWP, forexample, based on or in response to reception of the PDCCH message forBWP switching other than successful contention resolution, and/or thewireless device (e.g., MAC entity of the wireless device) deciding toperform BWP switching. The wireless device (e.g., MAC entity of thewireless device) may continue with the ongoing RA procedure on theactive BWP, for example, based on the wireless device deciding to ignorethe PDCCH message for BWP switching.

The wireless device (e.g., MAC entity of the wireless device), for eachactivated serving cell, may start or restart a BWP inactivity timer(e.g., bwp-InactivityTimer) associated with the active DL BWP. The startor restart may be based on the BWP inactivity timer (e.g.,bwp-InactivityTimer) being configured, the default downlink BWPparameter (e.g., defaultDownlinkBWP) being configured, and/or the activeDL BWP is not the BWP indicated by the the default downlink BWPparameter (e.g., defaultDownlinkBWP). The start or restart may be basedon the the default downlink BWP parameter (e.g., defaultDownlinkBWP) notbeing configured, and/or the active DL BWP not being the the initialdownlink BWP parameter (e.g., initialDownlinkBWP). The start or restartmay be based on a PDCCH message addressed to C-RNTI or CS-RNTIindicating downlink assignment or uplink grant is received on the activeBWP. The start or restart may be based on a PDCCH message addressed toC-RNTI or CS-RNTI indicating downlink assignment or uplink grant beingreceived for the active BWP. The start or restart may be based on a MACPDU being sent (e.g., transmitted) in a configured uplink grant, and/orreceived in a configured downlink assignment: if there is no ongoing RAprocedure associated with this serving cell; and/or if the ongoing RAprocedure associated with this serving cell is successfully completedupon reception of this PDCCH message addressed to C-RNTI.

The wireless device (e.g., MAC entity of the wireless device), for eachactivated serving cell, may start or restart the BWP inactivity timer(e.g., bwp-InactivityTimer) associated with the active DL BWP, forexample, based on the BWP inactivity timer (e.g., bwp-InactivityTimer)being configured, the default downlink BWP parameter (e.g.,defaultDownlinkBWP) being configured, and/or the active DL BWP is notthe BWP indicated by the default downlink BWP parameter (e.g.,defaultDownlinkBWP). The start or restart may be based on the thedefault downlink BWP parameter (e.g., defaultDownlinkBWP) not beingconfigured, the active DL BWP not being the the initial downlink BWPparameter (e.g., initialDownlinkBWP), a PDCCH message for BWP switchingbeing received on the active DL BWP, and/or the wireless device (e.g.,MAC entity of the wireless device) switching the active BWP.

The wireless device (e.g., MAC entity of the wireless device), for eachactivated serving cell, may stop the BWP inactivity timer (e.g.,bwp-InactivityTimer) associated with the active DL BWP of this servingcell, if running, for example, based on the BWP inactivity timer (e.g.,bwp-InactivityTimer) being configured, the default downlink BWPparameter (e.g., defaultDownlinkBWP) being configured, and the active DLBWP not being the BWP indicated by the default downlink BWP parameter(e.g., defaultDownlinkBWP), the the default downlink BWP parameter(e.g., defaultDownlinkBWP) not being configured, the active DL BWP notbeing the the initial downlink BWP parameter (e.g., initialDownlinkBWP),and/or RA procedure being initiated on this serving cell. The wirelessdevice (e.g., MAC entity of the wireless device) may stop the BWPinactivity timer (e.g., bwp-InactivityTimer) associated with the activeDL BWP of SpCell, if running, for example, based on if the serving cellis SCell

The wireless device (e.g., MAC entity of the wireless device) mayperform BWP switching to a BWP indicated by the the default downlink BWPparameter (e.g., defaultDownlinkBWP), for example, based on the BWPinactivity timer (bwp-InactivityTimer) being configured, the the defaultdownlink BWP parameter (e.g., defaultDownlinkBWP) being configured,and/or the active DL BWP is not the BWP indicated by the the defaultdownlink BWP parameter (e.g., defaultDownlinkBWP). The wireless device(e.g., MAC entity of the wireless device) may perform BWP switching to aBWP indicated by the the default downlink BWP parameter (e.g.,defaultDownlinkBWP), for example, based on the the default downlink BWPparameter (e.g., defaultDownlinkBWP) not being configured, the active DLBWP not being the the initial downlink BWP parameter (e.g.,initialDownlinkBWP), the BWP inactivity timer (e.g.,bwp-InactivityTimer) associated with the active DL BWP expiring, and/orthe the default downlink BWP parameter (e.g., defaultDownlinkBWP) beingconfigured. Otherwise the wireless device (e.g., MAC enity) may performBWP switching to the the initial downlink BWP parameter (e.g.,initialDownlinkBWP).

A wireless device, configured for operation in BWPs of a serving cell,may be configured by higher layers for the serving cell a set of at mosta first threshold value (e.g., 4, 8, 16, 32 or any other quantity) ofBWPs for reception by the wireless device in a DL bandwidth (e.g., a DLBWP set) by a BWP downlink parameter (e.g., BWP-Downlink) and a set ofat most a second threshold value (e.g., 4, 8, 16, 32 or any otherquantity) BWPs for transmissions by the wireless device in an ULbandwidth (e.g., a UL BWP set) by a BWP uplink parameter (e.g.,BWP-Uplink) for the serving cell.

An initial active DL BWP may be defined by a location and number ofcontiguous PRBs, a subcarrier spacing, and a cyclic prefix, for thecontrol resource set for a downlink common search space (e.g.,Type0-PDCCH common search space). A wireless device may be provided(e.g., configured with, indicated by, etc.) an initial active UL BWP bya higher layer initial uplink BWP parameter (e.g., initialuplinkBWP) forexample, for operation on the primary cell or on a secondary cell Thewireless device may be provided (e.g., configured with, indicated by,etc.) an initial UL BWP on the supplementary carrier by a higher layerinitial uplink BWP parameter (e.g., initialUplinkBWP) in a supplementaryuplink, for example, based on the wireless device being configured witha supplementary carrier.

The wireless device may be provided by (e.g., configured by, indicatedby, etc.) a higher layer first active downlink BWP index parameter(e.g., firstActiveDownlinkBWP-Id) a first active DL BWP for receptionand, by a higher layer first active uplink BWP index parameter (e.g.,firstActiveUplinkBWP-Id), a first active UL BWP for transmissions on theprimary cell, for example, based on a wireless device having a dedicatedBWP configuration.

The wireless device may be configured with the following parameters forthe serving cell for each DL BWP or UL BWP in a set of DL BWPs or ULBWPs, respectively: a subcarrier spacing provided by (e.g., configuredby, stored in, indicated by, etc.) a parameter (e.g., a higher layerparameter such as, for example, subcarrierSpacing); a cyclic prefixprovided by (e.g., configured by, stored in, indicated by, etc.) aparameter (e.g., a higher layer parameter such as, for example,cyclicPrefix); a first PRB and a number of contiguous PRBs indicated bya parameter (e.g., a higher layer parameter such as, for example,locationAndBandwidth) that may be interpreted as RIV, setting N_(BWP)^(size)=275, and the first PRB being a PRB offset relative to the PRBindicated by parameters (e.g., a higher layer parameter such as, forexample, offsetToCarrier and subcarrierSpacing); an index in the set ofDL BWPs or UL BWPs via a parameter (e.g., a higher layer parameter suchas, for example, bwp-Id); and/or a set of BWP-common and a set ofBWP-dedicated parameters via parameters (e.g., a higher layer parametersuch as, for example, bwp-Common and bwp-Dedicated).

A DL BWP from the set of configured DL BWPs with index provided by(e.g., configured by, indicated by, etc.) higher layer BWP indexparameter (e.g., bwp-Id) for the DL BWP is linked with an UL BWP fromthe set of configured UL BWPs with index provided (e.g., configured by,indicated by, etc.) by higher layer BWP index parameter (e.g., bwp-Id)for the UL BWP if the DL BWP index and the UL BWP index are equal, forexample, based on unpaired spectrum operation A wireless device may notexpect to receive a configuration where the center frequency for a DLBWP is different than the center frequency for an UL BWP if the BWPindex parameter (bwp-Id) of the DL BWP is equal to the bwp-Id of the ULBWP, for example, based on unpaired spectrum operation.

A wireless device may be configured control resource sets for every typeof common search space and for wireless device-specific search space,for example, for each DL BWP in a set of DL BWPs on the primary cell.The wireless device may not expect to be configured without a commonsearch space on the PCell, or on the PSCell, in the active DL BWP. Thewireless device may be configured resource sets for PUCCH transmissions,for example, for each UL BWP in a set of UL BWPs.

A wireless device may receive PDCCH messages and PDSCH messages via a DLBWP according to a configured subcarrier spacing and CP length for theDL BWP. A wireless device may send (e.g., transmit) PUCCH messages andPUSCH messages via an UL BWP according to a configured subcarrierspacing and CP length for the UL BWP.

A field (e.g., a BWP indicator field) value may indicate the active DLBWP, from the configured DL BWP set, for DL receptions, for example,based on a BWP indicator field being configured in DCI format 1_1. TheBWP indicator field value may indicate the active UL BWP, from theconfigured UL BWP set, for UL transmissions, for example, based on a BWPindicator field being configured in DCI format 0_1.

The wireless device may prepend zeros to the information field until itssize is the one required for the interpretation of the information fieldfor the UL BWP or DL BWP prior to interpreting a DCI format 0_1 or DCIformat 1_1 information fields, respectively, for example, based on a BWPindicator field being configured in DCI format 0_1 or DCI format 1_1and/or indicating an UL BWP or a DL BWP different from the active UL BWPor DL BWP, respectively, for each information field in the received DCIformat 0_1 or DCI format 1_1; and/or the size of the information fieldbeing smaller than the one required for the DCI format 0_1 or DCI format1_1 interpretation for the UL BWP or DL BWP that is indicated by the BWPindicator, respectively. The wireless device may use a number of leastsignificant bits of DCI format 0_1 or DCI format 1_1 equal to the onerequired for the UL BWP or DL BWP indicated by BWP indicator prior tointerpreting the DCI format 0_1 or DCI format 1_1 information fields,respectively, for example, based on the size of the information fieldbeing larger than the one required for the DCI format 0_1 or DCI format1_1 interpretation for the UL BWP or DL BWP that is indicated by the BWPindicator, respectively. The wireless device may set the active UL BWPor DL BWP to the UL BWP or DL BWP indicated by the BWP indicator in theDCI format 0_1 or DCI format 1_1, respectively.

A wireless device may expect to detect a DCI format 0_1 indicatingactive UL BWP change, or a DCI format 1_1 indicating active DL BWPchange, for example, based on a corresponding PDCCH message beingreceived within a first threshold (e.g., 3, 4, 5, or any other quantity)of symbols of a slot.

A wireless device may be provided by (e.g., configured by, indicated by,etc.) a higher layer default downlink BWP index parameter (e.g.,defaultDownlinkBWP-Id) a default DL BWP among the configured DL BWPs,for example, for the primary cell The default DL BWP may be the initialactive DL BWP, for example, based on a wireless device not beingprovided (e.g., configured by, indicated by, etc.) a default DL BWP byhigher layer default downlink BWP index parameter (e.g.,defaultDownlinkBWP-Id.)

A wireless device may be configured for a secondary cell with higherlayer default downlink BWP index parameter (e.g., defaultDownlinkBWP-Id)indicating a default DL BWP among the configured DL BWPs.The wirelessdevice may be configured with higher layer BWP inactivity timerparameter (e.g., bwp-InactivityTimer) indicating a timer value. Thewireless device procedures on the secondary cell may be the same as onthe primary cell, using a timer value for the secondary cell and thedefault DL BWP for the secondary cell.

The wireless device may increment a timer every interval of a firstduration (e.g., 1 millisecond or any other duration) for frequency range1, or every second duration (e.g., 0.5 milliseconds or any otherduration) for frequency range 2, for example, based on the wirelessdevice being configured by higher layer BWP inactivity timer parameter(e.g., bwp-InactivityTimer), a timer value for the primary cell and thetimer is running, the wireless device not detecting a DCI format forPDSCH reception on the primary cell for paired spectrum operation, ifthe wireless device not detecting a DCI format for PDSCH reception,and/or a DCI format for PUSCH transmission on the primary cell forunpaired spectrum operation during the interval. A wireless device mayincrement a timer every interval of a first duration (e.g., 1millisecond or any other duration) for frequency range 1 or every secondduration (e.g., 0.5 milliseconds or any other duration) for frequencyrange 2, for example, based on a wireless device being configured byhigher layer BWP inactivity timer parameter (e.g., BWP-InactivityTimer),a timer value for a secondary cell, the timer being running, thewireless device not detecting a DCI format for PDSCH reception on thesecondary cell for paired spectrum operation, the wireless device notdetecting a DCI format for PDSCH reception, and/or a DCI format forPUSCH transmission on the secondary cell for unpaired spectrum operationduring the interval. The wireless device may deactivate the secondarycell if the timer expires.

The wireless device may use the indicated DL BWP and the indicated ULBWP on the secondary cell as the respective first active DL BWP andfirst active UL BWP on the secondary cell or supplementary carrier, forexample, based on a wireless device being configured by a higher layerfirst active downlink BWP index parameter (e.g.,firstActiveDownlinkBWP-Id), a first active DL BWP, and by higher layerfirst active uplink BWP index parameter (e.g., firstActiveUplinkBWP-Id),and/or a first active UL BWP on a secondary cell or supplementarycarrier. A wireless device does not expect to send (e.g., transmit)HARQ-ACK information on a PUCCH resource indicated by a DCI format 1_0or a DCI format 1_1, for example, based on paired spectrum operation,the wireless device changes its active UL BWP on the PCell between atime of a detection of the DCI format 1_0 or the DCI format 1_1, and/ora time of a corresponding HARQ-ACK information transmission on thePUCCH. A wireless device may not expect to monitor or continue tomonitor PDCCH if the wireless device performs RRM via a bandwidth thatis not within the active DL BWP for the wireless device.

A type of LBT procedure (e.g., CAT1, CAT2, CAT3, and/or CAT4) may beconfigured via control messages (e.g., RRC, MAC CE, and/or DCI) per acell, for example, in an unlicensed band. a type of LBT procedure (e.g.,CAT1, CAT2, CAT3, and/or CAT4) may be configured via control messages(e.g., RRC, MAC CE, and/or DCI) per BWP. A type of LBT procedure (e.g.,CAT1, CAT2, CAT3, and/or CAT4) may be determined at least based on anumerology configured in a BWP. BWP switching may change a type of LBTprocedure.

A wireless device may be configured (e.g., by a base station) with oneor more UL carriers associated with one DL carrier of a cell. One of oneor more UL carriers configured with a DL carrier may be referred to as asupplementary uplink (SUL) carrier or a normal UL (NUL or may bereferred to as a non-SUL) carrier. A base station may enhance ULcoverage and/or capacity by configuring an SUL carrier. A base stationmay configure a BWP configuration per an uplink (e.g., per uplinkcarrier) associated with a cell. One or more BWPs on an SUL may beconfigured (e.g., by a base station) separately from one or more BWPs ona NUL. A base station may control an active BWP of an SUL independentlyof an active BWP of a NUL. A base station may control two or more uplinktransmissions on two or more ULs (e.g., NUL and SUL) to avoidoverlapping PUSCH transmissions in time.

A base station may avoid configuring parallel uplink transmissions via aSUL and an NUL of a cell, wherein the parallel uplink transmissions maybe PUCCH transmissions (and/or PUSCH transmissions) via SUL and PUCCHtransimssions (and/or PUSCH) via NUL. A base station may send (e.g.,transmit) one or more RRC message (e.g., wireless device specific RRCsignaling) to configure and/or reconfigure a location of a PUCCHtransmissions on an SUL carrier and/or on a NUL carrier. A wirelessdevice may receive (e.g., from a base station) one or more RRC messagescomprising configuration parameters for a carrier. The configurationparameters may indicate at least one of: an RA procedure configuration,BWP configurations (e.g., number of DL/UL BWPs, a bandwidth and/or indexof configured DL/UL BWP, and/or initial, default, and/or active DL/ULBWP), a PUSCH configuration, a PUCCH configuration, an SRSconfiguration, and/or a power control parameter.

An SUL carrier and a NUL carrier may be configured (e.g., by a basestation) to support a RA procedure (e.g., initial access). Support for aRA to a cell configured with SUL is shown in FIG. 12, described above. ARACH configuration 1210 of an SUL may be configured (e.g., by a basestation) independent of a RACH configuration 1210 of an NUL. One or moreparameters associated with Msg1 1220, Msg 2 1230, Msg 3 1240, and/orcontention resolution 1250 via an SUL may be configured independent ofone or more parameters associated with Msg1 1220, Msg 2 1230, Msg 31240, and/or contention resolution 1250 via an NUL. One or moreparameters associated with PRACH transmissions in Msg 1 1220 via an SULmay be independent of one or more parameters associated with PRACHtransmission via an NUL.

A wireless device may determine which carrier (e.g., between NUL andSUL) to use, for example, based on an RA procedure in licensed bandsand/or a measurement (e.g., RSRP) of one or more DL pathloss referencesA wireless device may select a first carrier (e.g., SUL or NUL carrier)if a measured quality (e.g., RSRP) of DL pathloss references is lessthan a broadcast threshold (e.g., an RRC parameter,rsrp-ThresholdSSB-SUL in FIG. 18). One or more uplink transmissionsassociated with the RA procedure may remain on the selected carrier, forexample, based on a wireless device selecting a carrier between SULcarrier and NUL carrier for an RA procedure.

An NUL and an SUL may be configured (e.g., by a base station) with aTAG. A wireless device may employ a TA value received during a RAprocedure via a second carrier (e.g., NUL) of the cell, for example,based on an uplink transmission of a first carrier (e.g., SUL) of acell.

FIG. 31 shows an example of a coverage of a cell configured with a DLand two ULs. A base station may configure a NUL and DL over a firstfrequency (e.g., high frequency). An SUL may be configured over a secondfrequency (e.g., low frequency) to support uplink transmission (e.g., interms of coverage and/or capacity) of a cell. A broadcast threshold(e.g., an RRC parameter, rsrp-ThresholdSSB-SUL) for a wireless device toselect a carrier may be determined such that a wireless device locatedoutside a NUL coverage 3110 but inside an SUL coverage 3120 may start aRA procedure via an SUL. A wireless device located inside a NUL coverage3110 may start a RA procedure via a NUL. A wireless device may use aRACH configuration associated with a selected carrier for a RAprocedure.

A wireless device may perform a contention based RA procedure and/or acontention free RA procedure. A wireless device may perform a RAprocedure on an UL selected based on a broadcast threshold (e.g.,rsrp-ThresholdSSB-SUL). A base station may not indicate (e.g.,explicitly) to the wireless device which carrier to start a RAprocedure. A base station may indicate which carrier a wireless deviceperforms a RA procedure by sending a RACH configuration with an SULindicator (e.g., 0 may indicates a NUL carrier, 1 may indicate an SULcarrier or vice versa). A base station may indicate (e.g., explicitly)to a wireless device which UL carrier is to be used for a contentionfree or contention based RA procedure. A base station may indicate acontention free RA procedure by sending a RACH configuration with adedicated preamble index. A base station may indicate a contention basedRA procedure by sending a RACH configuration without a dedicatedpreamble index.

It may be beneficial for a network to receive one or more measurementsof NUL carrier(s) and/or SUL carrier(s) to initiate a (contention freeor contention based) RA procedure for a wireless device. A base stationmay configure a wireless device (e.g., a wireless device in RRCConnected) with one or more measurements on one or more DL referencesignals associated with NUL carrier(s) and/or SUL carrier(s) of a cell.

A base station may select a carrier between NUL carrier(s) and/or SULcarrier(s), for example, based on the quality of the one or moremeasurements and/or if a wireless device sends quality information ofone or more measurements on one or more DL reference signals associatedwith NUL carrier(s) and/or SUL carrier(s). A base station may indicate,to a wireless device, a selected carrier via RRC signaling (e.g.,handover) and/or PDCCH order (e.g., SCell addition) for initiating a(contention free or contention based) RA procedure. For load balancingbetween NUL carrier(s) and/or SUL carrier(s), a base station may selectone of NUL and SUL carrier by taking into consideration congestion inNUL carrier(s) and/or SUL carrier(s). A base station may better select acarrier (e.g., NUL or SUL) of a target cell for a (contention free orcontention based) RA procedure for a handover, for example, based on oneor more measurement reports associated with NUL carrier(s) and/or SULcarrier(s). A base station may better select a carrier (e.g., NUL orSUL) of an SCell (e.g., if the SCell is configured with at least a NULcarrier and an SUL carrier) for a (contention free or contention based)RA procedure for an SCell addition, for example, based on one or moremeasurement reports associated with NUL carrier(s) and/or SULcarrier(s).

A source base station may make a decision on a handover to one or moretarget cells, for example, for a handover of a wireless device. A sourcebase station may indicate a handover decision to a target base stationassociated with one or more target cells that the source base stationselects. A target base station may indicate to a wireless device (e.g.,through a cell of a source gNB) which carrier (between NUL carrier(s)and SUL carrier(s)) to use via a handover command. A handover commandreceived by a wireless device may comprise an SUL indicator (e.g., 1bit) along with one or more RACH parameters (e.g., dedicated preambleindex, and/or PRACH mask index), wherein the SUL indicator may indicateif the one or more RACH parameters are associated with an SUL or NULcarrier.

It may be useful that a source base station informs a target basestation about measured results on NUL carrier(s) and SUL carrier(s),e.g., high frequency carrier(s) and low frequency carrier(s), so thatthe target base station determines a carrier on which a wireless devicemay perform a (contention free or contention based) RA procedure for ahandover. The source base station may need to know whether SULcarrier(s) is (are) configured in the target gNB, and/or which carrieris allowed to be used for a handover, for example, if a source basestation configures DL measurements on one or more cells association witha NUL carrier(s) and/or SUL carrier(s) of a target gNB. A target basestation may inform a source base station of one or more configurationsof NUL carrier(s) and/or SUL carrier(s) of one or more cells in thetarget gNB. A source base station may configure DL measurement on one ormore cells in the target gNB, based on one or more configurationsindicating carrier configurations at the one or more cells in the targetgNB.

A base station may be aware of whether SUL carrier(s) is (are)configured in an SCell, and/or which carrier is allowed to be used foran SCell addition. A base station may configure DL measurements on NULcarrier(s) and/or SUL carrier(s). A base station may configure awireless device with one or more RACH configurations for an SCell, e.g.,a first RACH configuration for an SUL carrier, a second RACHconfiguration for a NUL carrier, and so on. A base station may send(e.g., transmit), to a wireless device via a PDCCH order comprising aparameter indicating in which carrier the wireless device starts a(contention free or contention based) RA procedure. A PDCCH ordertriggering a (contention free or contention based) RA procedure maycomprise one or more parameters indicating at least one of at least onepreamble (e.g., preamble index), one or more PRACH resources (e.g.,PRACH mask index), an SUL indicator, and/or a BWP indicator. A wirelessdevice receiving a PDCCH order may send (e.g., transmit) at least onepreamble via one or more PRACH resources of a BWP indicated by a BWPindicator of a carrier indicated by an SUL indicator, for example, for aRA procedure.

A wireless device may determine a RA procedure unsuccessfully completed.The wireless device may consider the RA procedure unsuccessfullycompleted, for example, if a wireless device receives no RARcorresponding to one or more preambles sent by the wireless deviceduring a RA procedure. There may be a number of preamble transmissionsallowed during a RA procedure (e.g., preambleTransMax in FIG. 20),wherein the number of preamble transmissions may be semi-staticallyconfigured by RRC. The wireless device may consider a RA procedureunsuccessfully completed, for example, if a wireless device receives noRAR corresponding to the number of preamble transmissions. A wirelessdevice may indicate a problem to upper layer(s), for example, after anunsuccessful completion of a RA procedure, and after the indicatedproblem. The upper layers(s) may trigger radio link failure that maylead to prolonged RA delay and degraded user experience.

A base station (source base station and/or a target gNB) configuring awireless device with a RACH configuration for a RA (for a handoverand/or SCell addition) may not allow to reuse the RACH configuration ifthe RA is unsuccessfully completed.

A failure of a (contention free or contention based) RA may result in along delay of RA. A wireless device may initiate a contention based RAprocedure, for example, if a contention free random access isunsuccessfully completed, instead of a contention free random access.The wireless device may perform an initial access to the target basestation based on a contention based random access, for example, if awireless device fails a contention free random access to a target basestation during a handover. A wireless device performing a contentionbased random access procedure may compete with one or more wirelessdevices to get an access to a gNB, which may not guarantee a success ofthe contention based random access procedure, and/or which may take long(e.g., four step procedure of the contention based random accessprocedure comparing with a contention free random access comprising MSG1 1220 and MSG 2 1230 transmissions) to receive a corresponding RAR.

The wireless device may wait until a base station sends a message (e.g.,PDCCH order) indicating a RACH configuration, for example, based onwhich the wireless device may initiate a RA for an SCell addition and/orif a wireless device fails a contention free random access for an SCelladdition. It may take long for a base station to detect a failure of aRA for an SCell addition. A wireless device may wait for a message(e.g., PDCCH order) sent to a base station for an SCell additionunnecessarily long.

FIG. 32 shows contention based and contention-free random accessprocedures with LBT. A successful contention based random accessprocedure may use Msg 1 3220, Msg 2 3230, Msg 3 3240, and contentionresolution 3250 to perform the RA procedure with the wireless device 110and base station 120. The wireless device may perform a first LBT,determine that the medium is clear, and send Msg 1 3220 to a basestation 120. The base station 120 may perform a second LBT, determinethat the medium is clear, and send Msg 2 3230 to the wireless device110. The wireless device 110 may perform a third LBT, determine themedium is clear, and send Msg 1 3240 to the base station 120. The basestation 1120 may perform a fourth LBT, determine that the medium isclear, and sends contention resolution 3250 to the wireless device 110.

A successful contention-free based RA procedure may use Msg 1 3220 andMsg 2 3230 to perform the RA procedure with the wireless device 110 andthe base station 120. The wireless device 110 may perform a first LBT,determine that the medium is clear, and send Msg 1 3220 to the basestation 120. The base station 120 may perform a second LBT, determinethat the medium is clear, and send Msg 2 3230 to the wireless device110.

A failure of a RA may occur due to LBT, for example, in an unlicensedband. At least one LBT may be performed prior to DL and/or ULtransmission. Msg 1 1220, Msg 2 1230, Msg 3 1240, and/or contentionresolution 1250 may require at least one LBT before the transmission(e.g., at least 4 LBTs), for example, in a contention based randomaccess procedure. Msg 1 1220 and Msg2 1230 may require at least one LBTeach (e.g., at least 2 LBTs), for example, for a contention-free randomaccess procedure. A base station and/or a wireless device may not send(e.g., transmit) a message (e.g., Msg 1 3220, Msg 2 3230, Msg 3 3240,and/or contention resolution 3250) for a RA procedure, for example, ifthe LBT procedure has failed prior to sending the message (e.g., CCA inLBT determines that a channel in unlicensed band is busy (e.g., occupiedby another device)).

A failure of an LBT procedure may result in degrading a user experience(e.g., in terms of QoS, capacity (e.g., throughput), and/or coverage). Abase station and/or a wireless device may wait until the channel becomesidle. This waiting may result in a latency problem to make a radio linkconnection between a base station and a wireless device. A failure of anLBT during a RA procedure may lead a long delay for a wireless device toreceive an UL grant and/or TA value from a base station. This delay mayresult in a call drop and/or traffic congestion. A failure of an LBTprocedure in a RA procedure for an SCell addition may lead a cellcongestion (e.g., load imbalancing) on one or more existing cells (e.g.,if an SCell may not take over traffic from the one or more existingcells in time).

An efficiency of RA procedure operating in an unlicensed band maydegrade with LBT failure, which may cause a latency/delay, and/orperformance degradation. Selecting two or more SSBs and performing oneor more LBT procedures via one or more PRACH occasions associated withthe two or more SSBs may increase a success rate of LBT procedures. Awireless device may measure a plurality of downlink reference signals(e.g., SSBs or CSI-RSs, if CSI-RS is configured by RRC). The wirelessdevice may select two or more SSBs by comparing RSRPs of the pluralityof downlink reference signals and a threshold. The threshold maycomprise a RSRP threshold SSB parameter (e.g., rsrp-ThresholdSSB) if theplurality of downlink reference signals are SSBs. The threshold maycomprise a RSRP threshold CSI-RS parameter (e.g., rsrp-ThresholdCSl-RS)if the plurality of downlink reference signals are CSI-RSs. The wirelessdevice may select two or more downlink referencing signals (SSBs orCSI-RSs) having RSRPs that are higher than the threshold. The wirelessdevice may determine one or more PRACH occasions associated with theselected two or more downlink reference signals (e.g., SSBs), forexample, based on SSBs being configured with the wireless device. Thewireless device may determine the one or more PRACH transmissions basedon an association between PRACH occasions and SSBs that may be indicatedby one or more RRC parameters (e.g., ra-ssb-OccasionMaskIndex). Thewireless device may determine one or more PRACH occasions associatedwith the selected two or more downlink reference signals (e.g.,CSI-RSs), for example, based on CSI-RSs being configured with thewireless device. The wireless device may determine the one or more PRACHtransmissions based on an association between PRACH occasions andCSI-RSs that may be indicated by one or more RRC parameters (e.g.,ra-OccasionList).

FIG. 33 is an example diagram of a two-step RA procedure with LBT. Atwo-step RA procedure may employ LBT in an unlicensed band. A basestation and/or a wireless device may not send (e.g., transmit) a message(e.g., two-step Msg 1 3320, preamble 3330, one or more TBs 3340, and/ortwo-step Msg 2 3350) for a RA procedure if LBT is failed prior tosending (e.g., transmitting) the message (e.g., CCA in LBT determinesthat a channel in unlicensed band is busy, e.g., occupied by otherdevice). The transmissions of the preamble 3330 and for one or more TBs3340 may have a same LBT procedure and/or different LBT procedures.

Radio resources for transmissions of a preamble 3330 and one or more TBs3340 may be configured in a same channel (or a same subband or a sameBWP or a same UL carrier), where a wireless device performs an LBTprocedure for the transmissions (e.g., based on a regulation). An LBTresult on the same channel (or the same subband or the same BWP or thesame UL carrier) may be applied for transmissions of the preamble 3330and for one or more TBs 3340.

FIG. 34 is an example of radio resource allocation for a two-step RAprocedure. PRACH resource 3430 and UL radio resources 3440 may betime-multiplexed, for example, based on a frequency offset in FIG. 34being zero. PRACH 3430 resource and UL radio resources 3440 may befrequency-multiplexed, for example, based on a timeoffset in FIG. 34being zero. The frequency offset in FIG. 34 may be an absolute number interms of Hz, MHz, and/or GHz, and/or a relative number (e.g., one ofindex from a set of frequency indices that arepredefined/preconfigured). The timeoffset in FIG. 34 may be an absolutenumber in terms of micro-second, milli-second, and/or second and/or arelative number (e.g., in terms of subframe, slot, mini-slot, OFDMsymbol). PRACH resource 3430 for transmission of the preamble 3330 andUL radio resources for transmission of one or more TBs 3340 may besubject to one LBT procedure if f1 3410 and f2 3420 are configured inthe same channel (or a same subband or a same BWP or a same UL carrier).One LBT procedure before a PRACH resource 3430 may be performed by awireless device (e.g., based on a regulation of unlicensed band). Aquantity of LBT procedures may be determined based on a value of thetimeoffset. One LBT procedure before a PRACH resource 3430 may beperformed by a wireless device, for example, if the value of a timeoffset is equal to and/or less than a threshold (e.g., that may beconfigured and/or defined by a regulation). The one LBT procedure maydetermine idle and a wireless device may perform a transmission of thepreamble 3230 via PRACH resource 3430 followed by a second transmissionof one or more TBs 3340 via the UL radio resources 3440 with no LBTprocedure (the transmission order may be switched if the UL radioresources 3440 is allocated before PRACH resource 3430 in time domain).PRACH and UL radio resources may be allocated closely enough in timedomain. A wireless device may perform a first LBT procedure before aPRACH resource 3430 and perform a second LBT procedure before U1 radioresources 3440, for example, based on the value of timeoffset beinglarger than the threshold

A bandwidth of BWP and/or UL carrier may be larger than a first value(e.g., 20 MHz). f1 3410 and f2 3420 may be configured in the bandwidth.A wireless device may perform an LBT procedure and apply a result (e.g.,idle or busy) of the LBT procedure to the transmission of the preamble3330 and UL radio resources for transmission of one or more TBs 3340. Awireless device may perform the transmissions of the preamble 3330 andfor one or more TBs 3340. If the channel is busy, a wireless device maynot perform the transmissions of the preamble 3330 and for one or moreTBs 3340, for example, based on the channel being idle.

A bandwidth of BWP and/or UL carrier may be less than a first value(e.g., 20 MHz). f1 3410 and f2 3420 may be configured in the bandwidth.A wireless device may perform an LBT procedure and apply a result (e.g.,idle or busy) of the LBT procedure to the transmission of the preamble3330 and UL radio resources for transmission of one or more TBs 3340. Awireless device may perform a first transmission of the preamble 3330followed by a second transmission of one or more TBs 3340, for example,based on if the channel being idle. A wireless device may not performthe transmissions of the preamble 3330 and for one or more TBs 3340, forexample, based on the channel being busy.

Radio resources for transmissions of the preamble 3330 and one or moreTBs 3340 may be configured in different channels, different subbands,different BWPs, and/or different UL carriers (e.g., one in NUL and theother one in SUL) that may require separate LBT procedures. A wirelessdevice may perform a LBT procedure per one or more channels, per one ormore subbands, per one or more BWPs, and/or per one or more UL carriers.

FIG. 35 shows an example of one or more LBT procedures performed for atwo-step RA procedure UL radio resources 3550 may be allocated before oraligned with PRACH resources 3530 in time. A wireless device may performa first LBT procedure (e.g., LBT 3540 in FIG. 35) before a firsttransmission of preamble 3330 (e.g., via PRACH resources 3530) andperform a second LBT procedure (e.g., LBT 3560 in FIG. 35) before asecond transmission of one or more TBs 3340 (e.g., via UL radioresources 3550). A wireless device may perform none of, one of, or bothof the first transmission and the second transmission, depending onresults of the first LBT procedure and second LBT procedure. SeparateLBTs before a PRACH message and/or data may provide benefits, such as:earlier transmission of the first transmission and/or secondtransmission by a wireless device, earlier transmission of a preamblethan if a larger LBT were used, and increased probability that atransmission will be successful.

The first transmission may be performed if a first result of the firstLBT procedure is idle. The second transmission may be independent of thefirst result. The second transmission may be performed if a secondresult of the second LBT procedure is idle. A wireless device may send(e.g., transmit) the preamble 3330, for example, in response to thefirst LBT procedure being idle. The wireless device may not be able tosend (e.g., transmit) one or more TBs 3340 in response to the second LBTprocedure being busy. A wireless device may not send (e.g., transmit)the preamble 3330 in response to the first LBT procedure being busy. Thewireless device may send (e.g., transmit) one or more TBs 3340 inresponse to the second LBT procedure being idle. In a two-step RAprocedure, one or more TBs may comprise an identifier of the wirelessdevice, for example, so that a base station may identify and/or indicatewhich wireless device sent (e.g., transmitted) the one or more TBs. Theidentity may be configured by the base station and/or may be at least aportion of wireless device-specific information (e.g., resume ID, DMRSsequence/index, IMSI, etc). A base station may identify and/or indicatethe wireless device based on the identity in the one or more TBs, forexample, based on a wireless device sending (e.g., transmiting) one ormore TBs with no preamble 3330 (e.g., if a channel, e.g. PRACH 3530 isbusy).

Separate LBT procedures for transmissions of a preamble and one or moreTBs may be performed, for example, based on a two-step RA procedureconfigured in an unlicensed band. A wireless device may be configured(e.g., by a base station) with separate LBT procedures for a widebandoperation (e.g., based on a bandwidth greater than 20 MHz). A wirelessdevice may be configured (e.g., by a base station) with a widebandcomprising one or more subbands and/or one or more BWPs, for example,based on wideband operation. Some of the one or more subbands mayoverlap in the frequency domain. Some of the one or more subbands maynot overlap in the frequency domain. Some of the one or more BWPsoverlap in the frequency domain. Some of the one or more BWPs may notoverlap in the frequency domain. Separate LBT procedures may be used fortransmissions via the two radio resources, for example, based on awideband operation and/or two radio resources being allocated with aspace larger than a threshold (e.g., 20 MHz). A wideband may compriseone or more subbands, and two radio resources may be allocated indifferent subbands. A first transmission scheduled in a first subbandmay use a first LBT procedure, and a second transmission scheduled in asecond subband may use an second LBT procedure. The first LBT procedureand the second LBT procedure may be independent of each other.

UL radio resources for transmission of one or more TBs 3340 may besubject to a first LBT procedure (e.g., LBT 3560) and be independent ofa second LBT procedure (e.g., LBT 3540) for transmission of the preamble3330. PRACH resources 3530 for transmission of the preamble 3330 may besubject to a second LBT procedure (e.g., LBT 3560) and be independent ofa first LBT procedure (e.g., LBT 3560) for transmission of one or moreTBs 3340. A wireless device may perform separate LBT procedures for afirst transmissions of the preamble 3330 and a second transmission ofone or more TBs 3340, for example, based on f1 3410 and f2 3420 beingconfigured in different channels, different subbands, different BWPs,and/or different UL carriers.

FIG. 36A and FIG. 36B are examples of one or more LBT proceduresperformed for a two-step RA procedure in an unlicensed band. Theresource allocation and the separate LBT procedures in FIG. 35 may beresulted from FIG. 36A and/or FIG. 36B. A wireless device may beconfigured (e.g., by a base station) with one or more PRACH resourcesand one or more UL radio resources in different channels (BWPs and/or ULcarriers). The wireless device may one or more first opportunities tosend (e.g., transmit) preambles and one or more second opportunities tosend (e.g., transmit) one or more TBs. A wireless device may have twoopportunities via random access resources (e.g., PRACH resource 3630 andPRACH resource 3530) for preamble transmission, for example, as shown inFIG. 36A. A wireless device may select one of two opportunities, forexample, based on LBT results. A wireless device may perform a first LBTprocedure (e.g., LBT 3640) and a second LBT procedure (e.g., LBT 3540 asshown in FIG. 36A). A wireless device may select one of PRACH resourcesassociated either a first LBT procedure or a second LBT procedure (e.g.,based on random selection), for example, based on the results of thefirst and second LBT procedures being idle. A wireless device may selecta PRACH resource associated with the LBT result being idle for preambletransmission, for example, based on one of LBT result being idle and theother of LBT result being busy. A wireless device may not send (e.g.,transmit) a preamble and may perform one or more LBT procedures for oneor more TB transmissions, for example, based on the first and second LBTprocedure results being busy.

A wireless device may have one or more opportunities for transmission ofone or more TBs via UL radio resources (e.g., in a similar way that awireless device has for preamble transmission above). The one or moreopportunities for transmission of one or more TBs may be independent ofone or more opportunities for transmission of preamble. The wirelessdevice may perform one or more LBT procedures to gain access to achannel to send (e.g., transmit) one or more TBs, for example, based ona wireless device not sending (e.g., transmitting) a preamble due to aresult (e.g., busy) of LBT procedure. A wireless device may perform afirst LBT procedure (e.g., LBT 3620) followed by a first transmissionopportunity of one or more TBs via first UL radio resources 3610 and asecond LBT procedure (e.g., LBT 3560 in FIG. 36A) followed by a secondtransmission opportunity of one or more TBs via second UL radioresources 3550, as shown in FIG. 36A. A wireless device may select oneof the opportunities, for example, depending on LBT results. A wirelessdevice may send (e.g., transmit) one or more TBs via UL radio resources3550, for example, based on LBT 3620 being busy and/or LTB 3560 beingidle as shown in FIG. 36A. A wireless device may not send (e.g.,transmit) any preamble, for example, based on one or more LBT procedures(e.g., LBT 3540 and LBT 3640 in FIG. 36A) to gain access for sending(e.g., transmitting) a preamble result in busy. A wireless device mayperform one or more second LBT procedures (e.g., LBT 3620 and LBT 3560in FIG. 36A) for transmission of one or more TBs.

The wireless device may receive, from a base station, one or morecontrol message (e.g., RRC messages and/or PDCCH messages) indicatingone or more associations between PRACH resources and UL radio resources,for example, before a wireless device initiates a two-step RA procedure.The associations may be one-to-one, multi-to-one, one-to-multi, and/ormulti-to-multi between one or more PRACHs resources and one or more ULradio resources. A wireless device may determine which UL radioresources and/or which PRACH resources to select, for example, based onthe associations. The associations may indicate one-to-multi associationfrom PRACH resource 3530 to UL radio resources 3550 and UL radioresources 3610, for example, as shown in FIG. 36A. The associations mayindicate one-to-one association from PRACH resources 3630 to UL radioresources 3550. A wireless device may perform one or more LBT procedures(depending on a regulation and/or resource allocation whether theresources are in the same channel) for transmission of one or more TBsdepending on a selection of PRACH resources. A wireless device mayperform two LBT procedures (LBT 3540 and LBT 3640), for example, asshown in FIG. 36A. A wireless device may send (e.g., transmit) apreamble via PRACH resources 3530, for example, based on LBT 3540 beingidle but LBT 3640 being busy. The wireless device may determine (e.g.,select) one or more candidate UL radio resources based on a configuredassociation of PRACH resources 3530, which may be one-to-multi fromPRACH resources 3530 to UL radio resources 3550 and UL radio resources3610. The wireless device may perform LBT 3620 and LBT 3560 based on theconfigured association. A wireless device may send (e.g., transmit) oneor more TBs, depending on the results of the LBT procedures. FIG. 36B isan example of a two-step RA procedure. UL radio resources are associatedwith one PRACH resource. An association may be configured (e.g., by abase station) from PRACH resource 3530 to UL radio resource 3550 and ULradio resources 3650.

The PRACH resource and/or UL radio resources in FIG. 34, FIG. 35, FIG.36A, and/or FIG. 36B may be associated with at least one referencesignal configuration (e.g., SSB, CSI-RS, DM-RS). A wireless device mayreceive (e.g., from a base station) at least one control message toindicate such an association. A configuration of each reference signalmay have an association with at least one PRACH resource, that may beconfigured by RRC message and/or PDCCH signals, for example, based onthe base station sending (e.g.,transmitting) a plurality of referencesignals. In one or more downlink channels, there may be a plurality ofPRACH resources and a plurality of UL radio resources associated withthe plurality of PRACH resources.

A failure of a LBT procedure may result in degrading a user experience(e.g., in terms of QoS, capacity (throughput), and/or coverage). A basestation and/or a wireless device may wait until the channel becomesidle. This wait may result in a latency problem to make a radio linkconnection between a base station and a wireless device. A failure of anLBT procedure during a RA procedure may lead a long delay for a wirelessdevice to receive an UL grant and/or TA value from a base station. Thisfailure may result in a call drop and/or traffic congestion. A failureof an LBT in a RA procedure for an SCell addition may lead to cellcongestion (e.g., load imbalancing) on one or more existing cells, forexample, because an SCell may not take over traffic from the one or moreexisting cells in time.

FIG. 37 shows an example of an association between downlink referencesignals and random access resource (e.g., PRACH) occasions. A basestation 120 may send a plurality (e.g., a burst, such as up to Kquantity) of DL reference signals 3702A-3702K. A wireless device 110 mayselect one or more random access resources (e.g., PRACH occasions3704A-3704K that may each correspond to at least one of a K quantity ofDL reference signals 3702A-3702K) to attempt a RA procedure (e.g., senda RAP). The wireless device 110 may perform the RA procedure on a firstavailable (e.g., clear) random access resource.

An association between a DL reference signal and random access resources(e.g., PRACH occasions) may be one-to-one mapping and/or multi-to-onemapping between DL reference signals and random access resourceoccasions (e.g., PRACH occasions). A wireless device 110 may measure kDL reference signals. A wireless device 110 may select DL referencesignal 1 3702A, DL reference signal 2 3702B, and DL reference signal 33702C. The wireless device 110 may perform up to a particular quantityof LBT procedures (e.g., at most 3 LBTs). Each LBT procedure may beperformed prior to each of the selected random access resource occasions(e.g., PRACH occasions), for example, if random access resource occasion(e.g., PRACH occasion) 1 3704A, random access resource occasion (e.g.,PRACH occasion) 2 3704B, and random access resource occasion (e.g.,PRACH occasion) 3 3704C are associated with DL reference signal 1 3702A,DL reference signal 2 3702B, and DL reference signal 3 3702C,respectively.

A type of LBT may be pre-defined and/or semi-statically by a basestation. A base station may indicate a type of LBT of random accessresource occasions (e.g., PRACH occasions) in a RACH configuration. Thetype may be one of CAT 1, CAT 2, CAT 3, CAT 4 (or long LBT and/or shortLBT).

A wireless device may send (e.g., transmit) one or more preambles viathe first random access resource occasion (e.g., PRACH occasion). Thewireless device may not perform one or more LBT procedures in otherrandom access resource occasions (e.g., PRACH occasions) that may beavailable after the first random access resource occasions (e.g., PRACHoccasions) in the same PRACH burst, for example, if an LBT successoccurs (e.g., channel is idle) in a first random access resourceoccasion (e.g., PRACH occasion). The wireless device may not performanother LBT procedure on random access resource occasion (e.g., PRACHoccasion) 3 3704C, for example, if the wireless device selects randomaccess resource occasion (e.g., PRACH occasion) 1 3704A and a randomaccess resource occasion (e.g., PRACH occasion) 3 3704C, and an LBTprocedure on random access resource occasion (e.g., PRACH occasion) 13704A is successful. The wireless device may perform one or more LBTprocedures prior to each of random access resource occasions (e.g.,PRACH occasions) in a first frequency (e.g., Freq. 1) at least until anLBT procedure is successful, for example, if a wireless device selectsall random access resource occasions (e.g., PRACH occasions) in thefirst frequency (e.g., Freq. 1 in FIG. 37). The wireless device may send(e.g., transmit) one or more preambles associated with a random accessresource occasion (e.g., PRACH occasion) if the LBT procedure issuccessful, for example, based on or in response to the LBT procedurebeing successful.

A wireless device may perform an LBT procedure for the one or morerandom access resource occasions (e.g., PRACH occasions) FDM-ed, whichmay be firstly available and/or may be randomly selected, for example,if one or more random access resource occasions (e.g., PRACH occasions)are frequency domain multiplexed (FDM-ed), e.g., random access resourceoccasion (e.g., PRACH occasion) 1 3704A and random access resourceoccasion (e.g., PRACH occasion) 2 3704B. A wireless device may (e.g.,based on RSRPs of DL reference signals) select random access resourceoccasion (e.g., PRACH occasion) 1 3704A and random access resourceoccasion (e.g., PRACH occasion) 2 3704B FDM-ed. The wireless device mayperform LBT procedure(s) on random access resource occasion (e.g., PRACHoccasion) 1 3704A and random access resource occasion (e.g., PRACHoccasion) 2 3704B. The wireless device may randomly select one of theserandom access resource occasions, for example, if both LBT proceduresare successful. The wireless device may select an available randomaccess resource occasion first in time domain, for example, if both LBTprocedures are successful. The wireless device may select a randomaccess resource occasion corresponding to a DL reference signal havingan RSRP that is greater than other DL reference signals, for example, ifboth LBT procedures are successful. Random access resource occasion(e.g., PRACH occasion) 1 3704A and random access resource occasion(e.g., PRACH occasion) 2 3704B may be FDM-ed within a threshold (e.g.,less than a bandwidth threshold). The wireless device may perform awideband LBT procedure that may cover a frequency range of random accessresource occasion (e.g., PRACH occasion) 1 3704A and random accessresource occasion (e.g., PRACH occasion) 2 3704B. The wireless devicemay select one of the random access resource occasions (e.g., PRACHoccasions) based on: a random selection, time location of random accessresource occasions (e.g., PRACH occasions), and/or RSRPs ofcorresponding DL reference signals, for example, if the wideband LBTprocedure is successful.

A wireless device may perform a long LBT on a first random accessresource occasion (e.g., PRACH occasion) firstly available. The wirelessdevice may perform a short LBT on a second random access resourceoccasion (e.g., PRACH occasion) following (e.g., after) the first randomaccess resource occasion (e.g., PRACH occasion), for example, if the LBTon the first random access resource occasion (e.g., PRACH occasion)fails (e.g., a long LBT procedure for random access resource occasion(e.g., PRACH occasion) 1 3704A fails and/or a short LBT procedure forrandom access resource occasion (e.g., PRACH occasion) 3 3704C fails). Atype of LBT procedure on the second random access resource occasion(e.g., PRACH occasion) may be configured by a base station. A type ofLBT procedure on the second random access resource occasion (e.g., PRACHoccasion) may be determined by a time difference of two random accessresource occasions (e.g., PRACH occasions). The first random accessresource occasion (e.g., PRACH occasion) and the second random accessresource occasion (e.g., PRACH occasion) may have a guard time less thana threshold (e.g., configurable or pre-defined, such as 25 μs, 16 μs, orany other duration). The wireless device may perform a short LBTprocedure on the second random access resource occasion (e.g., PRACHoccasion), for example, if the first random access resource occasion andthe second random access resource occasion have a guard time less than athreshold. The wireless device may perform a long LBT procedure, forexample, if the first random access resource occasion and the secondrandom access resource occasion have a guard time greater than or equalto the threshold.

The wireless device 110 may perform an LBT procedure before eachselected random access resource occasion, for example, at least untilsuccessful or until an LBT procedure before each of the selected randomaccess resource occasions have failed. The wireless device 110 mayperform a RA procedure on a random access resource occasion associatedwith a successful LBT procedure. The two or more random access resourceoccasions (e.g., PRACH occasions) 3704A-3704F may not be aligned.

A wireless device may select two or more random access resourceoccasions (e.g., PRACH occasions), for example, based on RSRPs of DLreference signals. A wireless device may select random access resourceoccasion (e.g., PRACH occasion) 1 3704A, random access resource occasion(e.g., PRACH occasion) 2 3704B, and/or random access resource occasion(e.g., PRACH occasion) 3 3704C. The wireless device may perform a firstLBT procedure on a first random access resource occasion (e.g., PRACHoccasion) available firstly in time (e.g., random access resourceoccasion (e.g., PRACH occasion) 1 3704A). The wireless device maydetermine a second LBT procedure on a second random access resourceoccasion (e.g., PRACH occasion), for example, based on the first LBTprocedure. The wireless device may send (e.g., transmit) a preamble viathe first random access resource occasion (e.g., PRACH occasion), forexample, if the first LBT procedure was successful. The wireless devicemay determine to perform a second LBT procedure on a second randomaccess resource occasion (e.g., PRACH occasion) available firstly afterthe first random access resource occasion (e.g., PRACH occasion) (e.g.,random access resource occasion (e.g., PRACH occasion) 2 3704B), forexample, if the first LBT procedure was not successful. The wirelessdevice may perform a third LBT procedure on a third random accessresource occasion (e.g., PRACH occasion), for example, if the second LBTprocedure on the second random access resource occasion (e.g., PRACHoccasion) has failed. The wireless device may perform a wideband LBT,for example, if one or more FDM-ed random access resource occasions(e.g., PRACH occasions) are configured within a guard time less than athreshold. The wireless device may perform LBT procedures on the one ormore FDM-ed random access resource occasions (e.g., PRACH occasions). Awireless device may send (e.g., transmit) a plurality of preambles via aplurality of random access resource occasions (e.g., PRACH occasions).

FIG. 38 shows an example one or more random access resource occasionconfigurations (e.g., PRACH occasions). The random access resourceoccasions may be separated by time and/or frequencies (e.g., TDM-edand/or FDM-ed). The random access resource occasions may be separated bygaps (e.g., PRACH occasions 3804A-3804D via freq. 1). The random accessresources may not be separated by gaps (e.g., PRACH occasions3804E-3804G via freq. 2). Groups of random access resources occasionsmay be separated by gaps (e.g., PRACH occasions 3804H-3804L via freq.3). The random access resources occasions may occur in differentfrequencies (e.g., PRACH occasions 3804A-3804D via freq. 1, PRACHoccasions 3804E-3804G via freq. 2, and/or PRACH occasions 3804H-3804Lvia freq. 3).

Random access resource occasions (e.g., PRACH occasions) may be timedivision multiplexed (TDM-ed) with a guard time (e.g., a time differenceor gap), for example, via Freq 1. A wireless device may perform an LBTprocedure in each random access resource occasion (e.g., PRACH occasion)in a first frequency (e.g., Freq. 1), for example, for multiple preambletransmissions. A wireless device may perform a long LBT procedure and/orshort LBT procedure, for example, depending on the guard time betweentwo random access resource occasions (e.g., PRACH occasions). A wirelessdevice may perform a short LBT procedure (or no LBT procedure) on arandom access resource occasion (e.g., PRACH occasion) available laterthan the other, for example, if the guard time (e.g., time difference)is less than a threshold (25 μs, 16 μs, or any other duration). Thewireless device may perform a long LBT procedure, for example, if theguard time (e.g., time difference) is greater than or equal to thethreshold. A type of LBT procedure in each random access resourceoccasion (e.g., PRACH occasion) may be configured by an RRC message. Atype of LBT procedure in each random access resource occasion (e.g.,PRACH occasion) may be determined by a wireless device by comparing witha guard time between random access resource occasions (e.g., PRACHoccasions) and the threshold.

One or more random access resource occasions (e.g., PRACH occasions) maybe TDM-ed without a guard time (or less than a threshold), for example,via a second frequency (e.g., Freq 2 in FIG. 38). A wireless device mayperform an LBT procedure on the first random access resource occasion(e.g., PRACH occasion) that occurs firstly among the selected randomaccess resource occasions (e.g., PRACH occasions) via the secondfrequency (e.g., Freq 2). A wireless device may avoid performing an LBTprocedure if the LBT on the first random access resource occasion (e.g.,PRACH occasion) was successful, for example, for subsequent randomaccess resource occasions (e.g., PRACH occasions) followed by the firstrandom access resource occasion (e.g., PRACH occasion) via the secondfrequency (e.g., Freq 2). The LBT procedure on the first random accessresource occasion (e.g., PRACH occasion) may be a long LBT procedure. AnLBT procedure on subsequent random access resource occasions (e.g.,PRACH occasions) may be a short LBT procedure if the LBT on the firstrandom access resource occasion (e.g., PRACH occasion) was successful. Awireless device may perform a long LBT or a short LBT, for example, ifthe selected random access resource occasions (e.g., PRACH occasions)are not contiguous in time. A type of LBT may be configured by a basestation and/or determined based on a time difference of the selectedrandom access resource occasions (e.g., PRACH occasions) that may benon-contiguous. One or more random access resource occasions (e.g.,PRACH occasions) may be grouped without a guard time, for example, via athird frequency (e.g., Freq 3 in FIG. 38). There may be a guard timebetween two groups as shown in random access resource occasion (e.g.,PRACH occasion) f3-2 3804I and random access resource occasion (e.g.,PRACH occasion) f3-3 3804J in FIG. 38. Similar procedures fordetermining an LBT procedure via a second frequency (e.g., Freq. 2) andvia a first frequency (e.g., Freq. 1) may be applied to the groupedPRACH occasions via the first frequency (e.g., Freq. 3), for example,using no LBT procedure, a long LBT procedure, or a short LBT procedure,for example, based on gaps and/or timing.

A wireless device may send (e.g., transmit), via a random accessresource occasion (e.g., PRACH occasion), a preamble (e.g., dedicatedpreamble or a preamble selected (e.g., randomly selected from aplurality of preambles) that may be configured by a base station (e.g.,if an LBT procedure is successful), for example, if a wireless deviceidentifies at least on clear channel based on the LBT procedure. Thewireless device may start to monitor a PDCCH channel for an RAR duringan RAR window, for example, after or in response to sending thepreamble. The wireless device may perform one or more preambletransmission attempts before starting the RAR window, for example,depending on one or more result(s) of one or more LBT procedures. Thewireless device may attempt a preamble transmission based on or inresponse to performing an LBT procedure. The wireless device may attemptanother preamble transmission based on or in response to the LBTprocedure having failed (e.g., a channel may be busy). The wirelessdevice may send (e.g., transmit) one preamble (e.g., may not performmultiple preamble transmissions), for example, before starting the RARwindow. A start timing of the RAR window may be determined based on timeindex of the random access resource occasion (e.g., PRACH occasion)and/or an offset (e.g., 3 TTIs predefined and/or semi-staticallyconfigured).

A wireless device may receive, from a base station, a message comprisingconfiguration parameters indicating: a plurality of reference signals;one or more preambles; an association between the plurality of referencesignals and the one or more preambles; and/or a first threshold. Thewireless device may select a plurality of first reference signals of theplurality of reference signals, wherein received signal strengths of theplurality of first reference signals may be greater than the firstthreshold. The wireless device may perform a first LBT procedurecorresponding to a first transmission of a first preamble, wherein thefirst preamble may be associated with at least a first one of theplurality of first reference signals. The wireless device may perform(e.g., based on or in response to a failure of the firstlisten-before-talk) a second LBT procedure corresponding to a secondtransmission of a second preamble, wherein the second preamble may beassociated with at least second one of the plurality of first referencesignals. The wireless device may send (e.g., transmit) the secondpreamble, for example, based on or in response to a success of thesecond LBT procedure.

A wireless device may start to monitor a downlink control channel, forexample, based on or in response to sending the second preamble. The oneor more reference signals may be synchronization signals. The one ormore reference signals may be channel state information referencesignals. The configuration parameters may indicate: one or more randomaccess channels; and/or an association between the one or more referencesignals and the one or more random access channels. A first radiochannel via which the first LBT procedure was performed may be TDM-edwith a second radio channel A first radio channel via which the firstLBT procedure was performed may be FDM-ed with a second radio channel. Afirst radio channel via which the first LBT was performed may be TDM-edand FDM-ed with a second radio channel The second preamble may be sentvia a random access channel associated with the at least second one ofthe plurality of reference signals. The first LBT procedure may be oneof a CAT1, CAT2, CAT3, and/or CAT4. The second LBT procedure may be oneof a CAT1, CAT2, CAT3, and/or CAT4.

The wireless device may send (e.g., transmit) at least one preamble viaa PRACH occasion (if a LBT procedure is successful) and/or at least oneTB via UL radio resources (if a LBT procedure is successful). Thewireless device may start to monitor or continue to monitor a DL controlchannel (e.g., PDCCH) for an RAR during an RAR window, for example,based on or in response to sending (e.g., transmitting) the preambleand/or the at least one TB.

FIG. 39A and FIG. 39B show examples of start timing of an RAR window.One or more methods may be used to determine start timing of the RARwindow, for example, using a RA contention resolution timer parameter(e.g., ra-ContentionResolutionTimer shown in FIG. 18) and/or a RARwindow parameter (e.g., ra-ResponseWindow shown in FIG. 20). Thewireless device may start the RAR window from the end of the preambletransmission with a time offset (e.g., configured and/or predefined),for example, based on a wireless device sending (e.g., transmiting) apreamble and a TB. The time offset may be zero. The wireless device maystart the RAR window from the end of the TB transmission with a timeoffset (configured and/or predefined), for example, based on a wirelessdevice sending (e.g., transmitting) a preamble and a TB. The wirelessdevice may start the RAR window from the end of the preambletransmission or the TB transmission, for example, whichever finishedlater as shown in FIG. 39A and FIG. 39B and/or based on a wirelessdevice sending (e.g., transmitting) a preamble and a TB. A wirelessdevice may perform at least two LBT procedures (one for preambletransmission, and the other one for TB transmission), and one of the atleast two LBT procedures may be successful (e.g., clear, unoccupied oridle). In this case, the wireless device may start the RAR window inresponse to determining a second LBT result of the at least two LBTprocedures being failed (e.g., busy or occupied). There may be a timeoffset (configured and/or predefined) before starting the RAR window.

FIG. 40A, FIG. 40B, and FIG. 40C show examples of start timing of RARwindow. A wireless device may send (e.g., transmit) a preamble without aTB transmission, for example, based on an LBT procedure for the preamblebeing idle and an LBT procedure for the TB transmission being busy. Awireless device may send (e.g., transmit) a TB without preambletransmission, for example, based on an LBT procedure for the preamblebeing busy and an LBT procedure for the TB transmission being idle.PRACH resources 4004 and UL radio resources 4002 in FIG. 40A, FIG. 40B,and FIG. 40C may be switched. An LBT procedure for preamble transmissionmay be successful but an LBT procedure for TB transmission may havefailed, for example, as shown in FIG. 40A. A wireless device may startthe RAR window with a time offset from either the end of preambletransmission or after the wireless device determines a failure of LBTprocedure for TB transmission, whichever finished later. A wirelessdevice may start the RAR window in response to the end of the preambletransmission with a time offset (e.g., that may be zero or any othervalue), for example, based on the preamble transmission finishing laterthan determining a failure of LBT procedure for TB transmission as shownin FIG. 40A. A wireless device may start the RAR window in response todetermining a failure of LBT procedure for TB transmission, for example,based on a failure of LBT procedure for TB transmission being determinedlater than the preamble transmission as shown in FIG. 40B. A PRACHresource 4004 may be associated with two UL radio resources 4002, asshown in FIG. 40C. A wireless device may start the RAR window fromeither the end of preamble transmission or after a wireless devicedetermines a failure of gaining access to channels of two UL radioresources 4002 for TB transmission. The two UL radio resources 4002 mayuse one LBT procedure or separate LBT procedures (each one locatedbefore a UL radio resource), for example, based on a configurationand/or regulation.

A wireless device may monitor or continue to monitor DL controlchannel(s) (e.g., PDCCH, dedicated CORESET, common search space, and/orwireless device-specific search space) to detect at least one RARcorresponding to at least one of a preamble 3330 (ifsent) and/or one ormore TBs 3350 (if sent), for example, within the RAR window. Thewireless device may determine that an RAR reception is not successful,for example, based on a wireless device receiving no RAR within the RARwindow. The wireless device may determine that an RAR reception is notsuccessful, for example, based on none of the RARs received by thewireless device comprising a preamble index (or indicator) indicatingthe preamble that the wireless device sends (e.g., transmits), and/orcomprising an identifier of the wireless device (e.g., sent via one ormore TBs).

FIG. 41 shows an example of determining a retransmission. The wirelessdevice may determine that an RAR reception is not successful, forexample, as part of a two-step RA procedure configured in unlicensedband andshown in FIG. 41. The wireless device may determine that an RARreception is not successful, for example, after the wireless devicesends (e.g., transmits) at least one preamble and/or sends (e.g.,transmits) at least one TB. The wireless device may determine that anRAR reception is not successful, for example, after the wireless devicesends (e.g., transmits) at least one preamble and/or does not send(e.g., transmit) at least one TB (e.g., due to a failure of LBTprocedure for a transmission of the at least one TB). The wirelessdevice may determine that an RAR reception is not successful, forexample, after the wireless device does not send (e.g., transmit) atleast one preamble (e.g., due to a failure of LBT for a transmission ofthe at least one preamble) and sends (e.g., transmits) at least one TB.A wireless device may attempt a retransmission of at least one preambleand/or at least one TB, for example, based on one or more failures(e.g., such as described above). The wireless device may increase apower (e.g., transmission power) for at least one preamble and/or atleast one TB transmission during the retransmission. A wireless devicemay attempt a retransmission of at least one preamble and/or at leastone TB, for example, after a failure of a transmission of at least onepreamble and at least one TB. One or more LBT procedures for the atleast one preamble and the at least one TB may fail, and the wirelessdevice may wait for a next one or more transmission occasions for aretransmission of the at least one preamble and the at least one TB. Thewireless device may not increase a power (e.g., transmission power) forat least one preamble and/or at least one TB transmission during theretransmission.

One or more methods may be used to increase the power (e.g.,transmission power) of a two step Msg 1 in a two-step RA procedure. Awireless device may increase a power ramping counter (e.g.,PREAMBLE_POWER_RAMPING_COUNTER) by one (or any other value or quantity).The power ramping counter may be shared between preamble transmissionand TB transmission of a two step Msg 1 in a two-step RA procedure. Thepower ramping counter may be employed for the preamble transmission in atwo-step RA procedure. Preamble transmission and TB transmission of atwo step Msg 1 may have separate power ramping counters. A wirelessdevice may increment both separate power ramping counters in a two-stepRA procedure. A wireless device may increment the separate power rampingcounters, for example, based on or in response to whether an associatedtransmission is performed in a two-step RA procedure. The wirelessdevice may increment a first power ramping counter for a preambletransmission, for example, if a retransmission of a two-step RAprocedure is based on or in response to a preamble transmission with aTB transmission and/or a corresponding RAR not being received. Thewireless device may increment a second power ramping counter for a TBtransmission, for example, if a retransmission is based on or inresponse to a preamble transmission with a TB transmission and/or acorresponding RAR not being received. The wireless device may incrementa first power ramping counter for a preamble transmission and may notincrement a second power ramping counter for a TB transmission, forexample, based on a retransmission of a two-step RA procedure being inresponse to a preamble transmission without a TB transmission and/or inresponse to no reception of corresponding RAR. The wireless device maynot increment a first power ramping counter for a preamble transmissionand may increment a second power ramping counter for a TB transmission,for example, based on a retransmission being in response to a TBtransmission without a preamble transmission and/or in response to noreception of corresponding RAR. A wireless device may determine anamount of power ramping, for example, based on a power ramping counterand/or a ramping step, such as: (power ramping counter-1)* ramping step.The ramping step may be shared between preamble and TB transmissions ofa two step Msg 1 in a two-step RA procedure.

A wireless device may determine a power (e.g., transmission power) basedon the updated power ramping counter, for example, for a preambletransmission. A preamble received target power parameter (e.g.,PREAMBLE_RECEIVED_TARGET_POWER) may be determined based on the preamblereceived target power parameter, delta preamble parameter, preamblepower ramping counter parameter and/or preamble power ramping stepparameter, such as: PREAMBLE_RECEIVED_TARGET_POWER topreambleReceivedTargetPower+DELTA_PREAMBLE+(PREAMBLE_POWER_RAMPING_COUNTER−1)×PREAMBLE_POWER_RAMPING_STEP).

A wireless device may determine, based on a preamble received targetpower parameter (e.g., PREAMBLE_RECEIVED_TARGET_POWER), a transmissionpower for a PRACH, P_(PRACHb,f,c)(i), on an active UL BWP b of a carrierf based on a current SS/PBCH block determination for serving cell c intransmission occasion i, such as:

P _(PRACHb,f,c)(i)=min{P _(CMAX,f,c)(i), P _(PRACH,target,f,c) +PL_(b,f,x)}[dBm],

in which: P_(CMAX,f,c)(i) may be the transmission power configured by abase station for a carrier f of a serving cell c within transmissionoccasion i, P_(PRACH,target,f,c) may be the PRACH preamble targetreception power parameter (e.g., PREAMBLE_RECEIVED_TARGET_POWER)provided (e.g., configured, indicated, etc.) above for the UL BWP b ofcarrier f of serving cell c, and PL_(b,f,c) may be a pathloss for the ULBWP b of carrier f for the current SS/PBCH block of serving cell cdetermined by the wireless device in dB as a reference signal parameter(e.g., referenceSignalPower—higher layer filtered RSRP). A referencesignal parameter (e.g., referenceSignalPower) may be provided by (e.g.,configured by, indicated by, etc.) an SS PBCH block power parameter(e.g., ss-PBCH-BlockPower), for example, based on the PRACH transmissionfrom the wireless not being based on a detection of a PDCCH order by thewireless device. A reference signal parameter (e.g.,referenceSignalPower) may be provided by (e.g., configured by, indicatedby, etc.) an SS PBCH block power parameter (e.g., ss-PBCH-BlockPower),for example, based on or in response to a detection of a PDCCH order bythe wireless device that triggers a contention based RA procedure.

A reference signal power parameter (e.g., referenceSignalPower) may beprovided by (e.g., configured by, indicated by, etc.) the SS PBCH blockpower parameter (e.g., ss-PBCH-BlockPower), for example, based on thePRACH transmission from the wireless device being in response to adetection of a PDCCH order by the wireless that triggers anon-contention based RA procedure, and/or the DL RS beingquasi-collocated with the DM-RS of the PDCCH order. A reference signalpower parameter (e.g., referenceSignalPower) may be obtained byparameters (e.g., a higher layer parameter such as, for example,parameter (e.g., a higher layer parameter such as, for example,ss-PBCH-BlockPower and powerControlOffsetSS), for example, after thewireless device may be configured resources for a periodic CSI-RSreception. A reference signal power parameter (e.g.,referenceSignalPower) may be obtained by parameter (e.g., a higher layerparameters such as, for example, ss-PBCH-BlockPower andpowerControlOffsetSS), for example, in which power control offset SSparameter (e.g., powerControlOffsetSS) may provide (e.g., configure,indicate, etc.) an offset of CSI-RS transmission power relative toSS/PBCH block transmission power. The wireless device may determine anoffset of 0 dB, for example, based on a power control offset SSparameter (e.g., powerControlOffsetSS) not being provided to (e.g.,configured by, indicated by, etc.) the wireless device.

A wireless device may determine a power (e.g., transmission power) forone or more TBs in a retransmission. The wireless device may determine apower (e.g., transmission power) based on a PUSCH power calculation. Anupdated power ramping counter may be used to update a preamble receivedtarget power parameter (PREAMBLE_RECEIVED_TARGET_POWER) for the powercalculation (e.g., PUSCH power calculation). Awireless device maydetermine a preamble received target power parameter (e.g.,PREAMBLE_RECEIVED_TARGET_POWER) based on preamble received target powerparameter, delta preamble parameter, preamble ramping counter parameter,preamble ramping step parameter (e.g.,preambleReceivedTargetPower+DELTA_PREAMBLE+(PREAMBLE_POWER_RAMPING_COUNTER−1)×PREAMBLE_POWER_RAMPING_STEP)).The preamble power ramping counter parameter (e.g.,PREAMBLE_POWER_RAMPING_COUNTER) may be replaced by another rampingcounter for the one or more TB transmission, if it exists (e.g., asdescribed above with two separate ramping counters).

A wireless device may determine power (e.g., PUSCH power), describedbelow, as a transmission power for one or more TBs for a retransmissionof a two-step RA procedure, for example, based on a preamble receivedtarget power (e.g., PREAMBLE_RECEIVED_TARGET_POWER). A wireless devicemay scale a linear value {circumflex over (P)}_(PUSCH ,f, c)(i,j, q_(d),l) of the power (e.g., transmit power) P_(PUSCH ,f ,c)(i, j, q_(d), l),with parameters in the following, by the ratio of the number of antennaports with a non-zero PUSCH transmission to the number of configuredantenna ports for the transmission scheme, for example, based on a PUSCHtransmission. The resulting scaled power may be split across the antennaports on which the non-zero PUSCH may be sent (e.g., transmitted). Theformula and one or more components in the formula may be defined perBWP.

The wireless device may determine the PUSCH transmission powerP_(PUSCH ,f ,c)(i, j, q_(d), l) in PUSCH transmission period i and basedon a wireless device sending (e.g., transmitting) a PUSCH on carrier fof serving cell c using parameter set configuration with index j andPUSCH power control adjustment state with index 1 , as

${P_{{PUSCH},f,c}\left( {i,j,q_{d},l} \right)} = {\min {\begin{Bmatrix}{{{P_{{CMAX},f,c}(i)},}\mspace{765mu}} \\{{P_{{O\_ {PUSCH}},f,c}(j)} + {10{\log_{10}\left( {2^{\mu} \cdot {M_{{RB},f,c}^{PUSCH}(i)}} \right)}} + {{\alpha_{f,c}(j)} \cdot {{PL}_{f,c}\left( q_{d} \right)}} + {\Delta_{{TF},f,c}(i)} + {f_{f,c}\left( {i,l} \right)}}\end{Bmatrix}\mspace{14mu}\lbrack{dBm}\rbrack}}$

P_(CMAX, f, c)(i) may be the configured wireless device power (e.g.,transmission power) for carrier f of serving cell c in PUSCHtransmission period i. P_(O_PUSCH, f, c)(j) may be (j) comprising thesum of a component P_(O_NOMINAL_ PUSCH, f, c)(j) and a componentP_(O_UE_PUSCH ,f, c)(j) where j∈{0, 1, . . . , J−1}. The wireless devicemay set P_(O_UE_PUSCH ,f,c)(0)=0, and P_(O_NOMINAL_ PUSCH, f ,c)(0)=P^(O_PRE)+Δ_(PREAMBLE_Msg 3), wherein the preamble initial receivedtarget parameter (e.g., preamblelnitialReceivedTargetPower) (forP_(O_PRE)) and delta preamble message three parameter (e.g.,Delta-preamble-msg3 or Δ_(PREAMBLE_Msg3)) may be provided by (e.g.,configured by, indicated by, etc.) higher layers for carrier f ofserving cell c, for example, based on a PUSCH transmission orretransmission corresponding to a RAR grant, j=0. A preamble messageparameter (e.g., Delta-preamble-msg3 or Δ_(PREAMBLE_Msg3)) may beconfigured at least for one or more TB transmission of two-step RAprocedure. If the preamble message parameter (e.g., Delta-preamble-msg3or Δ_(PREAMBLE_Msg3)) is configured only for a Msg3 1240, a wirelessdevice may ignore this value for determining a PUSCH power for one ormore TB transmissions in a two-step RA procedure. A PUSCH transmissionor retransmission may correspond to a grant-free configuration orsemi-persistent grant, and j=1, P_(O_NOMINAL_PUSCH, f, c)(1) may beprovided by (e.g., configured by, indicated by, etc.) a parameter (e.g.,a higher layer parameter such as, for example,p0-nominal-pusch-withoutgrant) and P_(O_UE_PUSCH, f ,c)(1) may beprovided by (e.g., configured by, indicated by, etc.) a parameter (e.g.,a higher layer parameter such as, for example, p0-ue-pusch for carrier)f of serving cell c. For j0∈{2, . . . , J−1}=S_(J), aP_(O_NOMINAL_PUSCH, f ,c)(j) value, applicable for all j∈S_(J), may beprovided by (e.g., configured by, indicated by, etc.) a parameter (e.g.,a higher layer parameter such as, for example, e.g.,p0-nominal-pusch-withgrant) for each carrier f of serving cell c and aset of P_(O_UE_PUSCH, f ,c)(j) values may be provided by (e.g.,configured by, indicated by, etc.) a set of one or more parameters(e.g., higher layer parameters such as, for example, e.g.,p0-pusch-alpha-set and a respective index by a parameter (e.g., a higherlayer parameter such as, for example, p0alphasetindex), for carrier f ofserving cell c where the size of the set may be J−2 and may be indicatedby a parameter (e.g., a higher layer parameter such as, for example,e.g., num-p0-alpha-sets).

M_(RB,f,c) ^(PUSCH)(i) may be a bandwidth of the PUSCH resourceassignment expressed in number of resource blocks for PUSCH transmissionperiod i on carrier f of serving cell c. μ may be predefined and/orsemi-statistically configured by one or more parameters.

For j=0, the wireless device may set α_(f ,c)(j)=1. For j=1, α_(f ,c)(1)may be provided by (e.g., configured by, indicated by, etc.) a parameter(e.g., a higher layer parameter such as, for example, e.g., alpha). Forj∈s, a set of α_(f ,c)(j) values may be provided by (e.g., configuredby, indicated by, etc.) a set of parameters (e.g., a higher layerparameter such as, for example, e.g., p0-pusch-alpha-set) and arespective index by a parameter (e.g., a higher layer parameter such as,for example, p0alphasetindex) for carrier f of serving cell c where thesize of the set may be J−2 and may be indicated by a parameter (e.g., ahigher layer parameter such as, for example, num-p0-alpha-sets).

PL_(f ,c)(q_(d)) may be a downlink path-loss estimate in dB determined(e.g., calculated) by the wireless device using a reference signal (RS)resource q_(d) for carrier f of serving cell c, in which the wirelessdevice may be configured with a quantity (e.g., number) of RS resourcesby one or more parameters (e.g., a higher layer parameter such as, forexample, num-pusch-pathlossReference-rs) and a respective set of RSconfigurations for the number of RS resources may be provided by (e.g.,configured by, indicated by, etc.) a parameter (e.g., a higher layerparameter such as, for example, pusch-pathloss-Reference-rs that maycomprise one or both of a set of SS/PBCH block indexes provided by(e.g., configured by, indicated by, etc.) a parameter (e.g., a higherlayer parameter such as, for example, pusch-pathlossReference-SSB) and aset of CSI-RS configuration indexes provided by (e.g., configured by,indicated by, etc.) a parameter (e.g., a higher layer parameter such as,for example, e.g., pusch-pathlossReference-CSIRS). The wireless devicemay indicate (e.g., identify) a RS resource in the set of RS resourcesto correspond to a SS/PBCH block or to a CSI-RS configuration asprovided by (e.g., configured by, indicated by, etc.) a parameter (e.g.,a higher layer parameter such as, for example, e.g.,pusch-pathlossreference-index). If the wireless device is configured bya parameter (e.g., a higher layer parameter such as, for example, e.g.,SRS-SpatialRelationlnfo), a mapping between a set of SRS resources and aset of RS resources for obtaining a downlink path-loss estimate, thewireless device may employ the RS resources indicated by a value of afield (e.g., a SRI field) in one or more DCI formats, e.g., DCI format0_0 or DCI format 0_1, that may schedule the PUSCH transmission toobtain the downlink path-loss estimate.

PL_(f,c)(q_(d)) may be based on a reference signal power parameter(e.g., referenceSignalPower) and a higher layer filtered RSRP parameter,for example, PL_(f ,c)(q_(d))=referenceSignalPower−higher layer filteredRSRP, in which the reference signal power parameter (e.g.,referenceSignalPower) may be provided by (e.g., configured by, indicatedby, etc.) higher layers and RSRP may be defined for the referenceserving cell and the higher layer filter configuration may be for thereference serving cell. For j=0, the the reference signal powerparameter (referenceSignalPower) may be configured by a parameter (e.g.,a higher layer parameter such as, for example, e.g., SS-PBCHBlockPower).For j>0, the the reference signal power parameter (referenceSignalPower)may be configured by a parameter (e.g., a higher layer parameter suchas, for example, e.g., SS-PBCHBlockPower) or, after periodic CSI-RStransmission may be configured, by a parameter (e.g., a higher layerparameter such as, for example, e.g., Pc-SS) providing (e.g.,configuring, indicating, etc.)an offset of the CSI-RS transmission powerrelative to the SS/PBCH block transmission power. A wireless device mayemploy a same RS resource index as for a corresponding PRACHtransmission, for example, based on the PUSCH transmission being an Msg31240 PUSCH transmission. A wireless device may employ a same RS resourceindex as for a corresponding PRACH transmission of preamble 1630, forexample, based on the PUSCH being one or more TB 1640. A wireless devicemay employ a same RS resource index as for a corresponding PRACHtransmission of preamble 1630, for example, based on the PUSCHtransmission being one or more TB 1640 and a base station not havingconfigured a RS resource index for the one or more TB transmissions1640. A wireless device may employ the configured RS resource index, forexample, based on a base station configuring an RS resource index forthe one or more TB transmission 1640 and if the PUSCH being one or moreTB 1640.

The wireless device may set Δ_(TF,f ,c)(i) as:

Δ_(TF,f ,c)(i)=10 log₁₀ (2^(BPRE·K) ^(S) −1)·β_(offset) ^(PUSCH))

For K_(s)=1.25 and Δ_(TF,f ,c)(i)=0 and for K_(s)=0, in which K_(s) maybe provided by (e.g., configured by, indicated by, etc.) a parameter(e.g., a higher layer parameter such as, for example, e.g.,deltaMCS-Enabled) provided (e.g., configured, indicated, etc.) for acarrier f and serving cell c. The wireless device may setΔ_(TF,f ,c)(i)=0, for example, based on the PUSCH transmission beingover more than one layers.

BPRE and β_(offset) ^(PUSCH), for a carrier f and a serving cell c, maybe computed as follows. The wireless device may set

${BPRE} = {\sum\limits_{r = 0}^{C - 1}\; {K_{r}\text{/}N_{RE}}}$

for PUSCH transmission with UL-SCH data and BPRE=O_(CSI)/N_(RE) for CSItransmission via a PUSCH resource without UL-SCH data, where C may bethe number of code blocks, K_(r) may be the size for code block r,O_(CSI) may be the number of CSI part 1 bits including CRC bits, andN_(RE) may be the number of resource elements determined asN_(RE)=M_(RB, f,c) ^(PUSCH)(i)·N_(symb,f,c) ^(PUSCH)(i) excluding REsused for DM-RS transmission, where N_(symb, f,c)(i) may be a number ofsymbols for PUSCH transmission period i on carrier f of serving cell cand C , K_(r) may be predefined and/or semi-statistically configured.The wireless device may set β_(offset) ^(PUSCH)=1 based on the PUSCHtransmission comprising UL-SCH data, and the wireless device may setγ_(offset) ^(PUSCH)=β_(offset) ^(CSI, 1) based on the PUSCH transmissioncomprising CSI and not including UL-SCH data.

For the PUSCH power control adjustment state for carrier f of servingcell c in PUSCH transmission period i , γ_(PUSCHf, c)(i−K_(PUSCH),l) maybe a correction value, also may be referred to as a TPC command, and maybe via a PDCCH transmission with one or more DCI formats (e.g., DCIformat 0_0 or DCI format 0_1) that may schedule the PUSCH transmissionperiod i on carrier f of serving cell c or jointly coded with other TPCcommands in a PDCCH transmission with one or more DCI formats (e.g., DCIformat 2_2) having CRC parity bits scrambled by a RNTI (e.g.,TPC-PUSCH-RNTI) that may be received by the wireless device prior to thePUSCH transmission.

The PUSCH power control adjustment state for carrier f of serving cell cin PUSCH transmission period i , f_(f ,c)(i, l)=f_(f ,c)(i−1,l)+δ_(PUSCH, f,c)(i−K_(PUSCH), l) may be the PUSCH power controladjustment state for carrier f of serving cell c and PUSCH transmissionperiod i based on accumulation being enabled based on an accumulationenabled parameter (e.g., Accumulation-enabled) provided by (e.g.,configured by, indicated by, etc.) higher layers, for example, in whichl∈{1, 2} if the wireless device is configured with a parameter (e.g., ahigher layer parameter such as, for example, e.g.,num-pusch-pcadjustment-states) otherwise, l=1. The value of l∈{1, 2} maybe provided (e.g., configured, indicated, etc.) to the wireless deviceby a parameter (e.g., a higher layer parameter such as, for example,e.g., PUSCH-closed-loop-index), for example, based on a PUSCH(re)transmission corresponding to a grant-free configuration orsemi-persistent grant. The wireless device may setδ_(PUSCHf, c)(i−K_(PUSCH), l)=0 dB if the wireless device may not detecta TPC command for carrier f of serving cell c. If the PUSCH transmissionis in response to a PDCCH decoding with a DCI format (e.g., DCI format0_0, DCI format 0_1, or DCI format 2_2) having CRC parity bits scrambledby a RNTI (e.g., TPC-PUSCH-RNTI) the respective δ_(PUSCH, f,c)accumulated values may be predefined. A wireless device may map a field(e.g., a TPC Command Field) (e.g., in DCI format 0_0, DCI format 0_1,DCI format 2_2, or DCI format 2_3) having CRC parity bits scrambled by aRNTI (e.g., TPC-PUSCH-RNTI or TPC-SRS-RNTI) to absolute and accumulatedδ_(PUSCH,c) values. f_(f ,c) (0, l) may be a first value after reset ofaccumulation. Positive TPC commands for carrier f of serving cell c maynot be accumulated, for example, based on the wireless device havingreached P_(CMAX,f,c)(i) for carrier f of serving cell c. Negative TPCcommands for carrier f of serving cell c may not be accumulated, forexample, based on a wireless device having reached minimum power forcarrier f of serving cell c. A wireless device may reset accumulationfor carrier f of serving cell c, after P_(O_UE_PUSCH ,f ,c)(j) value ischanged by higher layers, and/or if α_(f ,c)(j) value is changed byhigher layers.

For the PUSCH power control adjustment state for carrier f of servingcell c in PUSCH transmission period i , f_(f ,c)(i,l)=δ_(PUSCH,f,c)(i−K_(PUSCH),l) may be the PUSCH power controladjustment state for carrier f of serving cell c and PUSCH transmissionperiod i based on accumulation not being enabled based on theaccumulation enabled parameter (e.g., Accumulation-enabled) provided by(e.g., configured by, indicated by, etc.) higher layers. If the PUSCHtransmission is in response to a PDCCH decoding with a DCI format (e.g.,DCI format 0_0, DCI format 0_1, or DCI format 2_2) having CRC paritybits scrambled by a RNTI (e.g., TPC-PUSCH-RNTI) the respectiveδ_(PUSCH,c) absolute values may be predefined. The wireless device mayset f_(f ,c)(i, l)=f_(f ,c)(i−1, l) for a PUSCH transmission periodwhere the wireless device may not detect a DCI format (e.g., DCI format0_0, DCI format 0_1, or DCI format 2_2), having CRC parity bitsscrambled by a RNTI (e.g., TPC-PUSCH-RNTI) for carrier f of serving cellc.

For the PUSCH power control adjustment state for carrier f of servingcell c in PUSCH transmission period i , and/or for both types off_(f ,c)(*) (accumulation or current absolute) the first value may beset as follows: If P_(O_UE_PUSCH ,f,c)(j) value is changed by higherlayers and/or serving cell c is the primary cell or, ifP_(O_UE_PUSCH ,f ,c)(j) value is received by higher layers and servingcell c is a secondary cell, the wireless device may set f_(f ,c)(0,l)=0.Else, if the wireless device receives the RAR message for carrier f ofserving cell c, the wireless device may setf_(f ,c)(0,l)=ΔP_(rampup,f ,c)=δ_(msg2,f ,c), in which δ_(msg 2,f ,c)may be the TPC command indicated in the RAR corresponding to the RAPsent (e.g., transmitted) for carrier f in the serving cell c, and

${\Delta \; P_{{rampup},f,c}} = {\min \left\lbrack {\left\{ {\max \left( {0,{P_{{CMAX},f,c} - \begin{pmatrix}{{10{\log_{10}\left( {2^{\mu} \cdot {M_{{RB},f,c}^{PUSCH}(0)}} \right)}} +} \\{{P_{{O\_ {PUSCH}},f,c}(0)} + {{\alpha_{f,c}(0)} \cdot {PL}_{c}} +} \\{{\Delta_{{TF},f,c}(0)} + \delta_{{{msg}\mspace{14mu} 2},f,c}}\end{pmatrix}}} \right)} \right\},{\Delta \; P_{{rampuprequested},c}}} \right\rbrack}$

and ΔP_(rampuprequ ested ,f ,c) may be provided by (e.g., configured by,indicated by, etc.) higher layers and corresponds to the total powerramp-up requested by higher layers from the first to the last RAP forcarrier f in the serving cell c, M_(RB,f,c) ^(PUSCH)(0) may be thebandwidth of the PUSCH resource assignment expressed in number ofresource blocks for the first PUSCH transmission in carrier f of servingcell c, and Δ_(TF ,f ,c)(0) may be the power adjustment of first PUSCHtransmission in carrier f of serving cell c. A power ramping counter maynot be shared between preamble and TB transmission in a two-step RAprocedure. ΔP_(rampuprequ ested ,f ,c) may correspond to the total powerramp-up requested from the first to the last TB transmissions forcarrier f in the serving cell c. A single power ramping counter may beshared between preamble and TB transmission in a two-step RA procedure.ΔP_(rampuprequ ested ,f ,c) may correspond to the total power ramp-uprequested from the first to the last radom access preamble for carrier fin the serving cell c.

A wireless device may receive, from a base station, a message comprisingconfiguration parameters of two step RA procedure. The configurationparameters may indicate: random access channel of a preambletransmission of the two step RA procedure; and/or uplink resources of adata transmission of the two step RA procedure. The wireless device mayperform: a first listen-before-talk of the preamble transmission; and asecond listen-before-talk of the data transmission. The wireless devicemay send (e.g., transmit) data via the uplink resources in response to:a failure of the first listen-before-talk; and/or a success of thesecond listen-before-talk. The wireless device may monitor or continueto monitor corresponding RAR during a RAR window. The wireless devicemay increment a power ramping counter of the preamble transmission, forexample, based on or in response to receiving no corresponding RAR. Thewireless device may start to monitor or continue to monitor a downlinkcontrol channel for the corresponding RAR, for example, based on or inresponse to sending (e.g., transmitting) the data.

PRACH and PUSCH transmissions may form a part of a two step RAprocedure. PRACH and PUSCH transmissions may be two-step Msg 1 (or MsgA)transmission of a two step RA procedure. RAR monitoring may start orcontinue after or in response to a PUSCH transmission. This proceduremay comprise different behavior from a four step RA procedure, as RARmonitoring may occur between PRACH and PUSCH.

FIG. 42 shows an example of a retransmission procedure with poweradjustment for a two step RA procedure. The procedure may be preformedby devices such as those shown in FIG. 1, including wireless devices 110and base stations 120. A wireless device may send (e.g., transmit) 4202at least one of a preamble or TB(s) on an unlicensed band or spectrum,for example, as a two step Msg 1 (e.g., MsgA) during a two step RAprocedure and/or based on a failure of at least one LBT procedure. Thewireless device may determine 4208 to perform a retransmission, forexample, based on a failure to receive a response and/or a contentionresolution that was not successful. The retransmission may comprise atleast one of a preamble transmission (e.g., preamble 4206 in FIG. 42)and/or a TB transmission (e.g., transport block 4204 in FIG. 42), forexample, a s two step Msg 1 (e.g., MsgA) retransmission. The wirelessdevice may determine a power (e.g., transmission power) of the preambleand/or TB for the retransmission. The wireless device may send (e.g.,transmit) the preamble 4206 and/or the TB 4204 with the determined power(e.g., transmission power) as a retransmission procedure. The wirelessdevice may perform a retransmission of a preamble and/or a TB. Thepreambles 4206 and 4202 may not be the same. TBs 4202 and 4204 may notbe the same.

An efficiency of an RA procedure operating in an unlicensed band maydegrade with LBT failure, which may cause a latency, delay, and/orperformance degradation of wireless communications. A failure of an LBTduring a RA procedure may lead to a long delay for a wireless device toreceive an UL grant and/or TA value from a base station. This delay mayresult in a call drop and/or traffic congestion. A failure of an LBTprocedure in a RA procedure for an SCell addition may lead a cellcongestion (e.g., load imbalancing) on one or more existing cells (e.g.,if an SCell may not take over traffic from the one or more existingcells in time). Increasing power to a retransmission during a RAprocedure may reduce a number of retransmissions, for example, such thatafter a medium may become available, the transmission may be less likelyto fail because of interference, low power, and/or other problemsrelated to transmission power. This increased power may allow a trade ofa decrease in latency, delay, call drop, and/or performance degradationfor a temporary increase in power consumption for a retransmission.

The wireless device may perform one of a preamble transmission and TBtransmission, for example, in a two step RA procedure, as a two step Msg1 (e.g., Msg A) transmission, based on one or more LBT proceduresperformed for the preamble transmission and/or based on the TBtransmission. A wireless device may send (e.g., transmit) a preamblewithout sending (e.g., transmitting) one or more TBs, for example, basedon an LBT procedure indicating that a channel (e.g., PUSCH) fortransmission of the one or more TBs is occupied (e.g., busy). A wirelessdevice may send (e.g., transmit) one or more TBs without sending (e.g.,transmitting) a preamble, for example, based on an LBT procedureindicating that a channel (e.g., PRACH) for transmission of the preambleis occupied (e.g., busy). The wireless device may determine aretransmission of a preamble and/or one or more TBs, for example, basedon no reception of RAR and/or a contention resolution being failed.

Problems in determining a transmission or retransmission power mayoccur, for example, if power is based on a quantity of transmissions orretransmissions (e.g., a quantity of preamble transmissions) performed.The quantity of retransmissions may comprise a quantity ofretransmissions (e.g., actual transmissions) performed, for example,based on an LBT procedure indicating a channel that is non-occupied(e.g., idle). The quantity of retransmissions may not comprise aquantity of retransmission attempts (e.g., a quantity of LBT proceduresperformed). The wireless device may increment one of preambletransmission or retransmission power and TB transmission orretransmission power, for example, based on no reception of RAR, acontention resolution being failed, and/or one of preamble transmissionor retransmission and TB transmission or retransmission (e.g., asdescribed above) being performed. Incrementing one of a preambletransmission or retransmission power and TB transmission orretransmission power may change one of PRACH and/or PUSCH uplinkcoverage and may result in a PRACH and/or PUSCH coverage mismatchproblem. One of PRACH and/or PUSCH coverages may be adjusted properly,for example, based on the incremented power but the other is not. One ofPRACH and/or PUSCH coverages may become too large (e.g., overshooting)but the other does not, for example, based on the incrementedtransmission power on one of preamble and TB transmissions. A basestation may receive one of a preamble and a TB (e.g., which transmittedwith an incremented transmission power) and may fail to receive theother of the preamble and the TB (e.g., which transmitted without anincremented transmission power). The base station may send, to awireless device, an indication to fallback to a four step RA procedureand/or retransmission of the other (e.g., which may be transmittedwithout an incremented transmission power) that the base stationcouldn't receive. This procedure may cause a latency, delay, and/orperformance degradation of wireless communications.

Carefully determining one or more parameter values (e.g., a rampingpower counter value) for a retransmission based on a type of RAprocedure (e.g., a two step RA procedure) and/or a result (success orfailure) of LBT procedure may reduce latency, delay, and/or performancedegradation of wireless communications. A power control mechanism forpreamble and TB transmission or retransmission of a two step RAprocedure may be used. The wireless device may determine aretransmission power of a first transmission (e.g., preambletransmission) based on a second transmission (e.g., TB transmission),for example, based on or in response to the first transmission not beingperformed in a previous transmission. The first transmission may not beperformed in a previous transmission, for example, based on one or moreLBT procedures indicating a first channel for the first transmissionbeing busy and a second channel for the second transmission being idle.The wireless device may determine a transmission or retransmission powerof the first transmission properly, for example, by referring the secondtransmission. This may result in a two step RA procedure completewithout an unnecessary one or more retransmissions. These procedures mayimprove a latency, delay, and/or battery power consumption.

The wireless device may determine a PRACH retransmission power and/or aPUSCH retransmission power, for example, based on a previoustransmission power of a PRACH transmission and/or a PUSCH transmission.The change in power from a prior transmission, or prior retransmission,to a next transmission may be referred to as power ramping. A powerramping counter may count a quantity of times a transmission and/orretransmission has failed. A power ramping step may provide (e.g.,configure, indicate, etc.) a value for which power may be changed. Powerramping of a transmission may be determined by multiplying a powerramping counter value by a power ramping step value. Power ramping of atransmission may be determined (e.g., calculated) by multiplying a powerramping counter value by a power ramping step value and adding a basevalue.

A wireless device may have separate power ramping counters and/or powerramping step values for a preamble transmission (e.g., which may be sentvia a PRACH resource) and a TB transmission (e.g., which may be sent viaa PUSCH resource). The wireless device may use a power ramping counterand/or power ramping step value associated with the resource (e.g.,PRACH resource or PUSCH resource) that failed and/or succeeded. Awireless device may use one power ramping counter and/or one powerramping step value; one power ramping counter and/or multiple powerramping step values, multiple power ramping counters and/or one powerramping step value; multiple power ramping counters and/or multiplepower ramping step values, or other configurations.

FIG. 43A and FIG. 43B show examples of retransmission procedures withpower adjustment and one or more LBT procedures. The retransmissionprocedures may be peformed by devices such as those shown in FIG. 1,including wireless devices 110 and base stations 120. FIG. 43A shows aretransmission procedure using power ramping based on a successfulpreamble transmission. An LBT procedure before a PRACH resource 4302 maybe successful (e.g., the medium is determined to be clear) and thewireless device may send a preamble via the PRACH resource 4302. An LBTprocedure before a PUSCH resource 4304 may be unsuccessful (e.g., themedium is determined to be busy) and the wireless device may send notransmission via the PUSCH resource 4304.

The wireless device may determine 4310 to perform a retransmission, forexample, based on a failure to receive a response and/or a contentionresolution that was not successful. The preamble transmission via thePRACH resource 4302 may be used to determine powers for transmission(e.g., transmit powers) of the preamble and TB for the retransmission. Apower ramping step value and/or a power ramping counter associated withthe PRACH resource 4302 may be used in determining (e.g., calculating)the powers for transmission (e.g., transmit powers) of theretransmissions of the preamble and TB.

The wireless device may perform a first LBT procedure before aretransmission of the preamble via a PRACH resource 4306. The wirelessdevice may send, or may not send, the retransmission of the preamble viaa PRACH resource 4306, for example, based on the outcome of the firstLBT procedure. The wireless device may perform a second LBT procedurebefore a retransmission of the TB via a PUSCH resource 4308. Thewireless device may send, or may not send, the retransmission of the TBvia the PUSCH resource 4308, for example, based on the outcome of thesecond LBT procedure.

FIG. 43B shows a retransmission procedure using power ramping based on asuccessful TB transmission. The retransmission procedures may bepeformed by devices such as those shown in FIG. 1, including wirelessdevices 110 and base stations 120. An LBT procedure before the PRACHresource 4312 may be unsuccessful (e.g., the medium is determined to bebusy) and the wireless device may send no transmission(s) via the PRACHresource 4312. An LBT procedure before the PUSCH resource 4314 may besuccessful (e.g., the medium is determined to be clear) and the wirelessdevice may send a TB transmission via the PUSCH resource 4314.

The wireless device may determine 4320 to perform a retransmission, forexample, based on a failure to receive a response and/or a contentionresolution that was not successful. The TB transmission via the PUSCHresource 4314 may be used to determine powers of transmissions (e.g.,transmission powers) of the preamble and TB for the retransmission. Apower ramping step value and/or a power ramping counter associated withthe PUSCH resource 4314 may be used in determining the powers oftransmissions (e.g., transmission powers) of the retransmission of thepreamble and TB.

The wireless device may perform a first LBT procedure before aretransmission of the preamble via a PRACH resource 4316. The wirelessdevice may send, or may not send, the retransmission of the preamble viaa PRACH resource 4316, for example, based on the outcome of the firstLBT procedure. The wireless device may perform a second LBT procedurebefore a retransmission of the TB via a PUSCH resource 4318. Thewireless device may send, or may not send, the retransmission of the TBvia the PUSCH resource 4318, for example, based on the outcome of thesecond LBT procedure.

FIG. 44 shows an example of a performing an RA retransmission procedurewith power adjustment. The retransmission procedures may be peformed bydevices such as those shown in FIG. 1, including wireless devices 110and base stations 120. At step 4402, a wireless device may initiate atwo-step RA procedure. At step 4404, the wireless device may perform afirst LBT for a preamble transmission via a PRACH resource and a secondLBT for a TB transmission via a PUSCH resource. At step 4406, thewireless device may determine that one of the first LBT and the secondLBT is successful. At step 4408, the wireless device may perform atransmission corresponding to the one of the first LBT and the secondLBT being successful. At step 4410, the wireless device may not receivea response to the transmission (e.g., RAR and/or contention resolution).At step 4412, the wireless device may determine a preambleretransmission and a TB retransmission. At step 4414, the wirelessdevice may determine, based on the transmission, powers of transmissions(e.g., transmission powers) of the preamble retransmission and the TBretransmission. At step 4416, the wireless device may perform, based onthe powers of transmissions (e.g., transmision powers), the preambleretransmission and the TB retransmission.

Alternatively, at step 4410, a wireless device may receive a response tothe transmission (e.g., RAR and/or contention resolution). At step 4418,a wireless device may determine that a two-step RA procedure completedsuccessfully.

FIG. 45 shows an example of responding to a RA retransmission procedurewith power adjustment. The retransmission procedures may be peformed bydevices such as those shown in FIG. 1, including wireless devices 110and base stations 120. At step 4502, a base station may send (e.g.,transmit) message(s) comprising configuration parameters for a two-stepRA procedure. At step 4504, the base station may attempt to receiveand/or detect at least one preamble transmission via a PRACH resourceand/or at least one TB transmission via a PUSCH resource based on theconfiguration parameters. At step 4506, the base station may identify atleast one wireless device performing a preamble transmission via a PRACHresource and/or a TB transmission via an uplink resource. At step 4508,the base station may send (e.g., transmit), to the at least one wirelessdevice, a response of the preamble transmission resource, and/or the TBtransmission.

Alternatively, at step 4506, a base station may not identify at leastone wireless device performing a preamble transmission via PRACH and/ora TB transmission. The base station may then return step 4504 andprocede as described.

A wireless device may perform a method comprising multiple operations.The wireless device may perform a first listen-before-talk (LBT)procedure for transmission of a first preamble of a first message. Thewireless device may perform a second LBT procedure for transmission ofthe first transport block of the first message. The wireless device may,based on a clear channel indicated by the second LBT procedure and abusy channel indicated by the first LBT procedure, transmit, using afirst transmission power, the first transport block. The wireless devicemay determine that a response to the first transport block has not beenreceived by a time duration. The wireless device may ramp, based on thefirst transmission power, a second transmission power and a thirdtransmission power. The wireless device may transmit, using the rampedsecond transmission power, the first preamble. The wireless device maytransmit, using the ramped third transmission power, a second transportblock.

The wireless device may also perform one or more additional operationsor include additional elements in conjunction with the described method.The wireless device may receive configuration parameters indicating afirst random access channel for transmission of the first preamble, anda first uplink channel for transmission of the first transport block.The wireless device may monitor, during a time duration, a downlinkcontrol channel for the response. The wireless device may determine,based on not receiving the response during the time duration, anunsuccessfully completed reception. The wireless device may ramp thesecond transmission power based on the unsuccessfully completedreception. The wireless device may determine that a contentionresolution is unsuccessfully completed based on not receiving theresponse. The wireless device may ramp the second transmission powerbased on the unsuccessfully completed contention resolution. Thewireless device may increment, based on transmitting the first transportblock, a first counter for transmission of the first preamble. Thewireless device may increment, based on transmitting the first transportblock, a second counter for transmission of the second transport block.The wireless device may ramp the second transmission power and the thirdtransmission power based on a prior transmission power.

A wireless device may perform a method comprising multiple operations.The wireless device may determine, based on a first listen-before-talk(LBT) procedure for transmission of a first preamble of a first message,a busy channel indication. The wireless device may determine, based on asecond LBT procedure and for transmission of a first transport block ofthe first message, a clear channel indication. The wireless device maytransmit, based on the clear channel indication, and using a firsttransmission power, the first transport block. The wireless device maydetermine that a time duration for receiving a response to the firsttransport block expired The wireless device may ramp, based on the firsttransmission power, a second retransmission power and a thirdretransmission power. The wireless device may transmit, using the rampedsecond transmission power, the first preamble. The wireless device maytransmit, using the ramped third transmission power, a second transportblock.

The wireless device may also perform one or more additional operationsor include additional elements in conjunction with the described method.The wireless device may receive configuration parameters indicating afirst random access channel for transmission of the first preamble; anda first uplink channel for transmission of the first transport block.The wireless device may monitor, during a time duration, a downlinkcontrol channel for the response. The wireless device may determine,based on not receiving the response during the time duration, anunsuccessfully completed reception. The wireless device may ramp, basedon the unsuccessfully completed reception, the second transmissionpower. The wireless device may determine, based on not receiving theresponse, that a contention resolution is unsuccessfully completed. Thewireless device may ramp, based on the unsuccessfully completedcontention resolution, the second transmission power. The wirelessdevice may increment, based on transmitting the first transport block, acounter for transmission of the first preamble. The wireless device mayincrement, based on transmitting the the first transport block, acounter for transmission of the second transport block. The wirelessdevice may ramp, based on a power ramping step value and a counter valueassociated with the transmission of the first transport block, thesecond transmission power and the third transmission power.

A wireless device may perform a method comprising multiple operations.The wireless device may determine, by a wireless device, that a firstrandom access channel resource, for transmission of a first preamble ofa first message, is occupied. The wireless device may transmit, via afirst uplink channel resource sensed as clear, a first transport blockof the first message. The wireless device may determine a power rampingcounter value based on transmitting the first transport block and on notreceiving a response to the first transport block. The wireless devicemay transmit, via a second random access channel resource, and using atransmission power based on the power ramping counter value, the firstpreamble. The wireless device may transmit, via a second uplink channelresource, a second transport block.

The wireless device may also perform one or more additional operationsor include additional elements in conjunction with the described method.The wireless device may receive, by the wireless device, a messagecomprising random access configuration parameters that indicate thefirst random access channel resource for transmission of the firstpreamble; and the first uplink channel resource for transmission of thefirst transport block. The wireless device may monitor, during a timeinterval, a downlink control channel for the response. The wirelessdevice may determine, based on not receiving the response during thetime interval, an unsuccessfully completed reception. The wirelessdevice may ramp, based on the unsuccessfully completed reception, thetransmission power. The wireless device may determine, completed basedon not receiving the response, that a contention resolution isunsuccessfully. The wireless device may ramp, based on theunsuccessfully completed contention resolution, the transmission power.The wireless device may increment, based on transmission of the firstpreamble via the second random access channel resource, a second powerramping counter value. The wireless device may base transmission poweron a power ramping step value and the power ramping counter value.

A wireless device may perform a method comprising multiple operations.The wireless device may perform a first listen-before-talk (LBT) fortransmission of a first preamble of a first message, the first messagecomprising the first preamble and a first transport block. The wirelessdevice may perform a second LBT for transmission of the transport block.The wireless device may determine that one of the first LBT or thesecond LBT indicates a clear channel The wireless device may determinethat another one of the first LBT or the second LBT indicates a busychannel. The wireless device may transmit one of the first preamble orthe transport block. The wireless device may determine a retransmissionof the first message based on not receiving a response to thetransmitting. The wireless device may ramp a first transmission powerand a second transmission power. The wireless device may transmit asecond preamble using the ramped first transmission power; and a secondtransport block using the ramped second transmission power.

The wireless device may also perform one or more additional operationsor include additional elements in conjunction with the described method.The one of the first preamble or the transport block may be the firstpreamble. The wireless device may transmit the preamble via the clearchannel. The one of the first preamble or the transport block may be thetransport block. The wireless device may transmit the transport blockvia the clear channel The wireless device may receive configurationparameters indicating a first random access channel for transmission ofthe first preamble; and a first uplink channel for transmission of thetransport block. The clear channel may be the first random accesschannel The one of the first preamble or the transport block may be thefirst preamble. The clear channel may be the first uplink channel Theone of the first preamble or the transport block may the transportblock. The wireless device may monitor a downlink control channel forthe response during a time interval starting in response to transmittingthe one of the first preamble or the transport block. The wirelessdevice may determine that reception of the response unsuccessfullycompleted based on not receiving the response. The wireless device mayramp in response to determining that reception of the responseunsuccessfully completed. The wireless device may determine that acontention resolution is unsuccessfully completed based on not receivingthe response. The wireless device may ramp in response to the contentionresolution. The wireless device may perform a third LBT for transmissionof the second preamble indicating a clear channel The wireless devicemay perform a fourth LBT for transmission of the transport blockindicating a clear channel. The wireless device may increment a firstcounter for transmission of the second preamble in response totransmitting the one of the first preamble or the transport block. Thewireless device may increment a second counter for transmission of thetransport block in response to transmitting the one of the firstpreamble or the transport block. The wireless device may increment athird counter for transmission of the second preamble and the transportblock in response to transmitting the one of the first preamble or thetransport block.

Systems, devices and media may be configured with the methods. Acomputing device may comprise one or more processors; and memory storinginstructions that, when executed, cause the computing device to performthe described method, additional operations and/or include theadditional elements. A system may comprise a first computing deviceconfigured to perform the described method, additional operations and/orinclude the additional elements; and a second computing deviceconfigured to receive the second preamble. A computer-readable mediummay store instructions that, when executed, cause performance of thedescribed method, additional operations and/or include the additionalelements.

FIG. 46 shows example elements of a computing device that may be used toimplement any of the various devices described herein, including, e.g.,the base station 122A and/or 122B, the wireless device 110 (e.g., 110Aand/or 110B), or any other base station, wireless device, or computingdevice described herein. The computing device 4600 may include one ormore processors 4601, which may execute instructions stored in therandom access memory (RAM) 4603, the removable media 4604 (such as aUniversal Serial Bus (USB) drive, compact disk (CD) or digital versatiledisk (DVD), or floppy disk drive), or any other desired storage medium.Instructions may also be stored in an attached (or internal) hard drive4605. The computing device 4600 may also include a security processor(not shown), which may execute instructions of one or more computerprograms to monitor the processes executing on the processor 4601 andany process that requests access to any hardware and/or softwarecomponents of the computing device 4600 (e.g., ROM 4602, RAM 4603, theremovable media 4604, the hard drive 4605, the device controller 4607, anetwork interface 4609, a GPS 4611, a Bluetooth interface 4612, a WiFiinterface 4613, etc.). The computing device 4600 may include one or moreoutput devices, such as the display 4606 (e.g., a screen, a displaydevice, a monitor, a television, etc.), and may include one or moreoutput device controllers 4607, such as a video processor. There mayalso be one or more user input devices 4608, such as a remote control,keyboard, mouse, touch screen, microphone, etc. The computing device4600 may also include one or more network interfaces, such as a networkinterface 4609, which may be a wired interface, a wireless interface, ora combination of the two. The network interface 4609 may provide aninterface for the computing device 4600 to communicate with a network4610 (e.g., a RAN, or any other network). The network interface 4609 mayinclude a modem (e.g., a cable modem), and the external network 4610 mayinclude communication links, an external network, an in-home network, aprovider's wireless, coaxial, fiber, or hybrid fiber/coaxialdistribution system (e.g., a DOCSIS network), or any other desirednetwork. Additionally, the computing device 4600 may include alocation-detecting device, such as a global positioning system (GPS)microprocessor 4611, which may be configured to receive and processglobal positioning signals and determine, with possible assistance froman external server and antenna, a geographic position of the computingdevice 4600.

The example in FIG. 46 may be a hardware configuration, although thecomponents shown may be implemented as software as well. Modificationsmay be made to add, remove, combine, divide, etc. components of thecomputing device 4600 as desired. Additionally, the components may beimplemented using basic computing devices and components, and the samecomponents (e.g., processor 4601, ROM storage 4602, display 4606, etc.)may be used to implement any of the other computing devices andcomponents described herein. For example, the various componentsdescribed herein may be implemented using computing devices havingcomponents such as a processor executing computer-executableinstructions stored on a computer-readable medium, as shown in FIG. 46.Some or all of the entities described herein may be software based, andmay co-exist in a common physical platform (e.g., a requesting entitymay be a separate software process and program from a dependent entity,both of which may be executed as software on a common computing device).

The disclosed mechanisms herein may be performed if certain criteria aremet, for example, in a wireless device, a base station, a radioenvironment, a network, a combination of the above, and/or the like.Example criteria may be based on, for example, wireless device and/ornetwork node configurations, traffic load, initial system set up, packetsizes, traffic characteristics, a combination of the above, and/or thelike. If the one or more criteria are met, various examples may be used.It may be possible to implement examples that selectively implementdisclosed protocols.

A base station may communicate with a mix of wireless devices. Wirelessdevices and/or base stations may support multiple technologies, and/ormultiple releases of the same technology. Wireless devices may have somespecific capability(ies) depending on wireless device category and/orcapability(ies). A base station may comprise multiple sectors. A basestation communicating with a plurality of wireless devices may refer tobase station communicating with a subset of the total wireless devicesin a coverage area. Wireless devices referred to herein may correspondto a plurality of wireless devices of a particular LTE or 5G releasewith a given capability and in a given sector of a base station. Aplurality of wireless devices may refer to a selected plurality ofwireless devices, and/or a subset of total wireless devices in acoverage area. Such devices may operate, function, and/or perform basedon or according to drawings and/or descriptions herein, and/or the like.There may be a plurality of base stations or a plurality of wirelessdevices in a coverage area that may not comply with the disclosedmethods, for example, because those wireless devices and/or basestations perform based on older releases of LTE or 5G technology.

One or more features described herein may be implemented in acomputer-usable data and/or computer-executable instructions, such as inone or more program modules, executed by one or more computers or otherdevices. Generally, program modules include routines, programs, objects,components, data structures, etc. that perform particular tasks orimplement particular abstract data types when executed by a processor ina computer or other data processing device. The computer executableinstructions may be stored on one or more computer readable media suchas a hard disk, optical disk, removable storage media, solid statememory, RAM, etc. The functionality of the program modules may becombined or distributed as desired. The functionality may be implementedin whole or in part in firmware or hardware equivalents such asintegrated circuits, field programmable gate arrays (FPGA), and thelike. Particular data structures may be used to more effectivelyimplement one or more features described herein, and such datastructures are contemplated within the scope of computer executableinstructions and computer-usable data described herein.

Many of the elements in examples may be implemented as modules. A modulemay be an isolatable element that performs a defined function and has adefined interface to other elements. The modules may be implemented inhardware, software in combination with hardware, firmware, wetware(i.e., hardware with a biological element) or a combination thereof, allof which may be behaviorally equivalent. For example, modules may beimplemented as a software routine written in a computer languageconfigured to be executed by a hardware machine (such as C, C++,Fortran, Java, Basic, Matlab or the like) or a modeling/simulationprogram such as Simulink, Stateflow, GNU Octave, or Lab VIEWMathScript.Additionally or alternatively, it may be possible to implement modulesusing physical hardware that incorporates discrete or programmableanalog, digital and/or quantum hardware. Examples of programmablehardware may comprise: computers, microcontrollers, microprocessors,application-specific integrated circuits (ASICs); field programmablegate arrays (FPGAs); and complex programmable logic devices (CPLDs).Computers, microcontrollers, and microprocessors may be programmed usinglanguages such as assembly, C, C++ or the like. FPGAs, ASICs, and CPLDsmay be programmed using hardware description languages (HDL), such asVHSIC hardware description language (VHDL) or Verilog, which mayconfigure connections between internal hardware modules with lesserfunctionality on a programmable device. The above-mentioned technologiesmay be used in combination to achieve the result of a functional module.

A non-transitory tangible computer readable media may compriseinstructions executable by one or more processors configured to causeoperations of multi-carrier communications described herein. An articleof manufacture may comprise a non-transitory tangible computer readablemachine-accessible medium having instructions encoded thereon forenabling programmable hardware to cause a device (e.g., a wirelessdevice, wireless communicator, a wireless device, a base station, andthe like) to allow operation of multi-carrier communications describedherein. The device, or one or more devices such as in a system, mayinclude one or more processors, memory, interfaces, and/or the like.Other examples may comprise communication networks comprising devicessuch as base stations, wireless devices or user equipment (wirelessdevice), servers, switches, antennas, and/or the like. A network maycomprise any wireless technology, including but not limited to,cellular, wireless, WiFi, 4G, 5G, any generation of 3GPP or othercellular standard or recommendation, wireless local area networks,wireless personal area networks, wireless ad hoc networks, wirelessmetropolitan area networks, wireless wide area networks, global areanetworks, space networks, and any other network using wirelesscommunications. Any device (e.g., a wireless device, a base station, orany other device) or combination of devices may be used to perform anycombination of one or more of steps described herein, including, forexample, any complementary step or steps of one or more of the abovesteps.

Although examples are described above, features and/or steps of thoseexamples may be combined, divided, omitted, rearranged, revised, and/oraugmented in any desired manner Various alterations, modifications, andimprovements will readily occur to those skilled in the art. Suchalterations, modifications, and improvements are intended to be part ofthis description, though not expressly stated herein, and are intendedto be within the spirit and scope of the descriptions herein.Accordingly, the foregoing description is by way of example only, and isnot limiting.

1. A method comprising: performing, by a wireless device, a firstlisten-before-talk (LBT) procedure for transmission of a first preambleof a message; performing a second LBT procedure for transmission of afirst transport block of the message; based on a clear channel indicatedby the first LBT procedure, transmitting the first preamble of themessage; based on a busy channel indicated by the second LBT procedure,determining not to transmit the first transport block of the message;determining, based on a determination that a response to the message hasnot been received by a time duration, a first ramped transmission powerand a second ramped transmission power; transmitting, using the firstramped transmission power, a second preamble; and transmitting, usingthe second ramped transmission power, the first transport block.
 2. Themethod of claim 1, further comprising: adjusting, based on thetransmitting the first preamble, a power ramping counter, wherein thedetermining the first ramped transmission power and the second rampedtransmission power is further based on the adjusted power rampingcounter.
 3. The method of claim 1, further comprising receivingconfiguration parameters that indicate: a first random access channelfor the transmission of the first preamble, and a first uplink channelfor the transmission of the first transport block.
 4. The method ofclaim 1, further comprising: monitoring, during the time duration, adownlink control channel for the response; and determining, based on notreceiving the response during the time duration, an unsuccessfullycompleted reception, wherein the determining the first rampedtransmission power and the second ramped transmission power is furtherbased on the unsuccessfully completed reception.
 5. The method of claim1, further comprising determining that a contention resolution isunsuccessfully completed based on not receiving the response, whereinthe determining the first ramped transmission power and the secondramped transmission power is further based on the unsuccessfullycompleted contention resolution.
 6. The method of claim 1, wherein thedetermining the first ramped transmission power and the second rampedtransmission power is further based on a prior transmission power of thetransmitting the first preamble.
 7. The method of claim 1, wherein thedetermining the first ramped transmission power and the secondtransmission power is further based on the transmitting the firstpreamble.